JPL Horizons ephemerides · Osculating elements
ssd-jpl-nasa-gov/ephemerides/osculating_elementsGet industry and reference data with JPL Horizons ephemerides · Osculating elements from Alexandria through one Spiral API key. Keplerian orbital elements of a planet, moon (center its planet, e.g. 599 for a Jupiter moon), asteroid, comet or spacecraft at a date. Default units au and days. It runs in the background and returns structured JSON. Pay as you go, with no subscription.
Pricing
$0.00873 per call.
Limits
- Runs
- In the background
- Returns
- json
- Longest queue wait
- 1 hour
- Run deadline
- 5 minutes
- Longest run, end to end
- 225 minutes
- Largest inline input
- 1 MB
- Largest input file
- 2 GB
- Largest output
- 5 GB
Input
| Field | Kind | Default | Description |
|---|---|---|---|
target required | text | — | Horizons target: an ID (499 Mars, 301 Moon, 399 Earth, 10 Sun, -31 Voyager 1, -170 JWST), an SPK ID from lookup_object (20099942 Apophis, 1000036 Halley), or a name/designation (Apophis, 2004 MN4). Ambiguous names fail with the candidates; resolve them with lookup_object. |
step | text | — | Step between rows: 30 m, 1 h, 6 h, 1 d, 1 mo, 1 y (default 1 d). At most 500 rows per call. |
stop | text | — | Stop time. Omit for one row at start. UTC for observer tables, TDB for vectors and elements: YYYY-MM-DD, YYYY-MM-DD HH:MM or YYYY-MM-DDTHH:MM:SSZ, years 1000 to 3000. |
start | text | — | Start time (or the single instant when stop is omitted; default now). UTC for observer tables, TDB for vectors and elements: YYYY-MM-DD, YYYY-MM-DD HH:MM or YYYY-MM-DDTHH:MM:SSZ, years 1000 to 3000. |
units | one of km_s, au_d | — | km_s or au_d. |
center | text | — | Central body: 10 Sun (default), 399 Earth (for the Moon or Earth satellites), 599 Jupiter, or site@body. |
reference_plane | one of ecliptic, equator | — | ecliptic (J2000 ecliptic, default) or equator (ICRF equatorial). |
Same request in code
curl https://api.spiral.ai/v1/runs \
-H "Authorization: Bearer $SPIRAL_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"provider": "alexandria",
"model": "ssd-jpl-nasa-gov/ephemerides/osculating_elements",
"input": {
"target": "<target>"
}
}'Frequently asked questions
How much does JPL Horizons ephemerides · Osculating elements cost?
$0.00873 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.
How do I use JPL Horizons ephemerides · Osculating elements through an API?
Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "ssd-jpl-nasa-gov/ephemerides/osculating_elements"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.
Do I need an account with Alexandria to use JPL Horizons ephemerides · Osculating elements?
No. Spiral runs it on its own Alexandria account and charges your Spiral balance.
Can my AI agent use JPL Horizons ephemerides · Osculating elements?
Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.