openephemeris-com · Schema
VenusStarPointsRequest
Request for computing Venus Star Points around a birth date.
CompanyAstrologyArtificial IntelligenceAstronomyData
Properties
| Name | Type | Description |
|---|---|---|
| beams_orb | number | Orb for under beams (default 17 degrees) |
| combust_orb | number | Orb for combustion (default 8.5 degrees) |
| exact_threshold | number | Threshold for 'exact' flag in degrees (default 1 arc min) |
| subject | object | Birth data (date, time, location) |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/openephemeris-com/json-schema/openephemeris-com-venus-star-points-request-schema.json",
"title": "VenusStarPointsRequest",
"description": "Request for computing Venus Star Points around a birth date.",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/openephemeris-com-venus-cycles-api-openapi.yml#/components/schemas/VenusStarPointsRequest",
"properties": {
"beams_orb": {
"default": 17,
"description": "Orb for under beams (default 17 degrees)",
"title": "Beams Orb",
"type": "number"
},
"combust_orb": {
"default": 8.5,
"description": "Orb for combustion (default 8.5 degrees)",
"title": "Combust Orb",
"type": "number"
},
"exact_threshold": {
"default": 0.0166,
"description": "Threshold for 'exact' flag in degrees (default 1 arc min)",
"title": "Exact Threshold",
"type": "number"
},
"subject": {
"allOf": [
{
"$ref": "#/$defs/SubjectRequest"
}
],
"description": "Birth data (date, time, location)"
}
},
"required": [
"subject"
],
"type": "object",
"$defs": {
"BirthLocation": {
"additionalProperties": false,
"description": "Location context for birth data: coordinates plus timezone.",
"properties": {
"city": {
"anyOf": [
{
"maxLength": 120,
"type": "string"
}
],
"description": "City name",
"title": "City"
},
"country": {
"anyOf": [
{
"maxLength": 120,
"type": "string"
}
],
"description": "Country",
"title": "Country"
},
"elevation": {
"anyOf": [
{
"type": "number"
}
],
"description": "Elevation in meters. Accepted and echoed back unchanged; it does not affect planetary positions, which are computed geocentrically. Elevation changes results only where it is taken as the `elev` query parameter: /eclipse/solar/local (local circumstances) and /time/solar-event plus /ephemeris/agro/* (horizon rise/set times).",
"title": "Elevation"
},
"latitude": {
"allOf": [
{
"$ref": "#/$defs/CoordinateInput"
}
],
"description": "Latitude coordinate"
},
"location_name": {
"anyOf": [
{
"maxLength": 200,
"type": "string"
}
],
"description": "Birthplace display name (e.g. \"Dallas, TX\"). Never affects calculations — coordinates and timezone are the only location facts the engine reads. Echoed back verbatim where the response carries an echo block: as subject.location_name on chart routes that echo a subject (natal, draconic, progressed, synastry, natal-transits, overlay, natal/batch items, predictive transit-chart), inside search_summary on /electional/natal-angle-crossings, metadata on /acg/midpoints, and natal on /human-design/transit-chart. Omitted from the response when not sent.",
"title": "Location Name"
},
"longitude": {
"allOf": [
{
"$ref": "#/$defs/CoordinateInput"
}
],
"description": "Longitude coordinate"
},
"region": {
"anyOf": [
{
"maxLength": 120,
"type": "string"
}
],
"description": "State/region",
"title": "Region"
},
"timezone": {
"allOf": [
{
"$ref": "#/$defs/TimezoneInput"
}
],
"description": "Timezone information"
}
},
"required": [
"latitude",
"longitude",
"timezone"
],
"title": "BirthLocation",
"type": "object"
},
"CoordinateInput": {
"additionalProperties": false,
"description": "Flexible coordinate input supporting multiple formats.",
"properties": {
"components": {
"anyOf": [
{
"additionalProperties": {
"anyOf": [
{
"type": "integer"
},
{
"type": "number"
},
{
"type": "string"
}
]
},
"type": "object"
}
],
"description": "Separate degree components with direction",
"title": "Components"
},
"decimal": {
"anyOf": [
{
"type": "number"
}
],
"description": "Decimal degrees (-90 to 90 for lat, -180 to 180 for lon)",
"title": "Decimal"
},
"dms": {
"anyOf": [
{
"maxLength": 64,
"type": "string"
}
],
"description": "Degrees, minutes, seconds string (e.g., '40°42'46\"N')",
"title": "Dms"
}
},
"title": "CoordinateInput",
"type": "object"
},
"DateTimeInput": {
"additionalProperties": false,
"description": "Date/time input in ISO-8601, component, or Julian day form. A value that states a clock time must also state its zone, either as a suffix on the string or via the `timezone` field below.",
"properties": {
"components": {
"anyOf": [
{
"additionalProperties": {
"type": "integer"
},
"type": "object"
}
],
"description": "Date/time components (year, month, day, and optionally hour, minute, second). If hour/minute are present, pass `timezone` alongside them; without it the request is rejected with 400 ambiguous_datetime. Omit the clock entirely and the date resolves to 12:00 UTC.",
"title": "Components"
},
"iso": {
"anyOf": [
{
"maxLength": 64,
"type": "string"
}
],
"description": "ISO-8601 datetime (supported range 1550–2650 CE, JPL DE440). If it states a clock time it must carry its zone: either a 'Z'/±HH:MM suffix on the string (\"1987-07-15T09:01:00-05:00\"), or a `timezone` passed alongside it. A zone-less clock time is rejected with 400 ambiguous_datetime — it is not read as UTC. A date-only value (\"1987-07-15\") has no clock to be ambiguous about and resolves to 12:00 UTC.",
"title": "Iso"
},
"julian_day": {
"anyOf": [
{
"format": "double",
"type": "number"
}
],
"description": "Julian Day Number (always UTC-based, so it needs no zone)",
"title": "Julian Day"
},
"timezone": {
"$ref": "#/$defs/TimezoneInput",
"description": "Zone the wall-clock time in `iso`/`components` belongs to, e.g. {\"iana_name\": \"America/Chicago\"}. Supply this to keep a local time as written instead of adding a UTC offset yourself. Ignored when the datetime already carries its own 'Z'/±HH:MM suffix."
}
},
"title": "DateTimeInput",
"type": "object"
},
"SubjectRequest": {
"additionalProperties": false,
"description": "Subject identity and birth data used to compute a chart.",
"properties": {
"birth_datetime": {
"allOf": [
{
"$ref": "#/$defs/DateTimeInput"
}
],
"description": "Birth date and time (alias: 'datetime')"
},
"birth_location": {
"allOf": [
{
"$ref": "#/$defs/BirthLocation"
}
],
"description": "Birth location details"
},
"gender": {
"anyOf": [
{
"maxLength": 32,
"type": "string"
}
],
"description": "Gender (optional)",
"title": "Gender"
},
"name": {
"description": "Subject name",
"maxLength": 120,
"minLength": 1,
"title": "Name",
"type": "string"
},
"notes": {
"anyOf": [
{
"maxLength": 1000,
"type": "string"
}
],
"description": "Additional notes",
"title": "Notes"
}
},
"required": [
"name",
"birth_datetime",
"birth_location"
],
"title": "SubjectRequest",
"type": "object"
},
"TimezoneInput": {
"additionalProperties": false,
"description": "Timezone input using IANA names or UTC offsets.",
"properties": {
"fold_preference": {
"description": "Which occurrence to use when the naive local datetime falls in a fall-back fold (a repeated hour): 'earlier' (default — first occurrence) or 'later'. Only meaningful for naive datetimes; the response reports datetime_status=ambiguous_fold either way so the ambiguity can be surfaced to the user.",
"enum": [
"earlier",
"later"
],
"title": "Fold Preference",
"type": "string"
},
"iana_name": {
"anyOf": [
{
"maxLength": 128,
"type": "string"
}
],
"description": "IANA timezone name",
"title": "Iana Name"
},
"time_standard": {
"description": "How to interpret a naive local datetime when this zone is applied. 'auto' (default): resolve through the historical-correction overlay where one covers the region/era, then IANA tzdata. 'standard': force the zone's standard (non-daylight) offset — for callers who KNOW the recorded time was standard time regardless of what tzdata believes. 'daylight': force standard+1h. Forcing either marks the resolution tz_confidence=client_override. Ignored when the datetime carries its own Z/±HH:MM suffix or when utc_offset is used.",
"enum": [
"auto",
"standard",
"daylight"
],
"title": "Time Standard",
"type": "string"
},
"utc_offset": {
"anyOf": [
{
"type": "number"
}
],
"description": "UTC offset in hours",
"title": "Utc Offset"
}
},
"title": "TimezoneInput",
"type": "object"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/openephemeris-com-venus-star-points-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.