Astro Agents vs Swiss Ephemeris vs computing it yourself

A comparison for astronomical data work: where a hosted, verifiable API saves you work, and where a local library is the better tool. Statements about other tools link to their own documentation.

Astro Agents APISwiss EphemerisDIY (Skyfield / SPICE + JPL file)
What it isA hosted HTTP API (REST and MCP) and a Python clientA C library (with bindings) you embed [source]Your own code on Skyfield or NASA's SPICE, with a JPL ephemeris file
EphemerisNASA/JPL DE440, served for 1800-2200Compressed files based on JPL DE441 [source]Any JPL ephemeris you download [JPL]
Agreement with JPLPositions within 0.024″ of JPL Horizons (ICRF), ecliptic longitudes as served within 0.062″ (1962-2026), on 12,400 published comparisons [benchmark]Its compressed files reproduce the JPL data to 0.001″, as stated by Astrodienst [source]That of the JPL file you load, if your frames and corrections are right
Event calendarBuilt in: eclipses with type, stations, lunations, separations, declination events, to the minuteBuilding blocks; the event search is yoursYours to write
Time zones and historical DSTResolved from the placeYours (the library takes UT/TT)Yours
ReproducibilitySHA-256 of every input and result; free /v1/verifyNot built inNot built in
LicenceUse under our terms; your code carries no licence obligationDual: GNU AGPL, or the Swiss Ephemeris Professional License bought from Astrodienst [source]Skyfield is MIT-licensed [source]; JPL ephemerides are public
CostFree key, then plans by card from $19 a month, or per callAGPL: free; professional licence: paid [source]Free
Offline and volumeNeeds the network; quotas and rate limitsOffline, unlimited; Astrodienst quotes 0.3 ms for a full set of planetary positions [source]Offline, unlimited
Best whenYou want the data now, in a notebook, an app or an agent, and want to cite itYou compute very many positions or ship an application offlineYou want full control and have the time

Accuracy and reproducibility are two different things

Accuracy is how close a position is to the truth. Ours comes from DE440 and is measured, not assumed: the benchmark compares 12,400 values with NASA/JPL Horizons. Swiss Ephemeris states 0.001″ against the JPL data it compresses; our served values are within 0.024″ (ICRF positions) and 0.062″ (ecliptic longitudes, 1962-2026) of Horizons. All of these are far below one arcsecond.

Reproducibility is getting the same bytes again. The SHA-256 on every result proves that a result is the one the API returned and that the same request returns it again; it does not prove that the result is accurate.

What you would have to build yourself

When to choose a library instead

If you need very many positions, must run offline, or ship an application, per-call pricing is the wrong tool: use Swiss Ephemeris (mind its licence) or Skyfield. If you want a ready event calendar and longitude series today, with a hash you can cite, the API is the short path.

Astronomical data only: no predictions, never a signal or forecast.

Time series & events API · Pricing