# JPL Horizons ephemerides · State vectors

Get industry and reference data with JPL Horizons ephemerides · State vectors from Alexandria through one Spiral API key. How far Voyager 1 is from the Sun or Earth, a spacecraft's speed, a planet's heliocentric or barycentric position for plotting or orbit work. Use center 399 for distance from Earth. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

- Provider: Alexandria
- Category: Industry Data
- Runs: In the background
- Returns: json
- Tool id: `alexandria` / `ssd-jpl-nasa-gov/ephemerides/state_vectors`
- Page: https://spiral.ai/tools/alexandria/ssd-jpl-nasa-gov/ephemerides/state_vectors

## Pricing

$0.00873 per call.

## Limits

- 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 | Allowed | 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 |  | — | Coordinate origin: 10 Sun center (default), 0 solar system barycenter, 399 Earth, 301 Moon, 5 Jupiter barycenter, or site@body (500@399). |
| `reference_plane` | one of | ecliptic, equator | — | ecliptic (J2000 ecliptic, default) or equator (ICRF equatorial). |

## Example

```bash
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/state_vectors",
    "input": {
      "target": "<target>"
    }
  }'
```

Try it in the Playground: https://spiral.ai/start?provider=alexandria&model=ssd-jpl-nasa-gov%2Fephemerides%2Fstate_vectors

## Common questions

### JPL Horizons ephemerides · State vectors

**How much does JPL Horizons ephemerides · State vectors 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 · State vectors through an API?**

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "ssd-jpl-nasa-gov/ephemerides/state_vectors"` 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 · State vectors?**

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

**Can my AI agent use JPL Horizons ephemerides · State vectors?**

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.

