vedicAPI
Accuracy

Check our numbers yourself.

We ran 1,000 test charts through vedicAPI and compared every planet with NASA JPL. Median gap 0.12″, largest 3.57″. We publish every input, our output and the difference, and run it again for every release.

1,000
test charts, 1900 to 2100
0.12″
median gap from NASA JPL
3.57″
largest gap, any planet

Tests use synthetic births only. Random dates, times and places. No customer or user data is ever used.

Last run 2026-11-21: 1,000 charts, 10,000 rows (all in the CSV; the table shows the first 20 charts and the 100 largest gaps).

Method

Four steps, every release.

  1. Step 1

    Generate inputs

    1,000 synthetic births with random dates from 1900 to 2100, random times, and places on every continent, including zones with daylight saving. No real people.

  2. Step 2

    Call vedicAPI

    Each birth goes to POST /v1/chart/planets, the same endpoint you call, with an API key. We keep the sidereal longitudes and the Lahiri ayanamsa.

  3. Step 3

    Compute the reference

    Independently, with open-source code and NASA JPL's planetary ephemeris: the apparent geocentric longitude of each planet, ecliptic of date, for the same UT moment.

  4. Step 4

    Publish the gap

    Our position plus the ayanamsa gives the tropical value. The difference from the reference, in arc seconds, goes into the table and the CSV.

Test table

Inputs, outputs and the gap.

Filter by body or reference, search an id, year or place, or sort by gap. Green is 1″ or less, amber is up to 3″.

Download CSV
  • Sun Synthetic #0001
    0.04″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Capricorn 27°35′13.5″
    JPL
    Capricorn 27°35′13.5″
  • Moon Synthetic #0001
    0.29″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Pisces 24°19′42.9″
    JPL
    Pisces 24°19′42.6″
  • Mars Synthetic #0001
    0.09″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Leo 18°17′02.4″
    JPL
    Leo 18°17′02.3″
  • Mercury Synthetic #0001
    0.11″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Capricorn 05°32′51.7″
    JPL
    Capricorn 05°32′51.6″
  • Jupiter Synthetic #0001
    0.11″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Scorpio 15°48′12.6″
    JPL
    Scorpio 15°48′12.4″
  • Venus Synthetic #0001
    0.11″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Pisces 11°44′09.9″
    JPL
    Pisces 11°44′09.8″
  • Saturn Synthetic #0001
    0.17″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Taurus 20°27′55.0″
    JPL
    Taurus 20°27′55.2″
  • Rahu Synthetic #0001
    0.13″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Libra 22°48′25.2″
    formula
    Libra 22°48′25.3″
  • Ketu Synthetic #0001
    0.13″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Aries 22°48′25.2″
    formula
    Aries 22°48′25.3″
  • Lagna Synthetic #0001
    1.68″
    2089-01-17 05:17 · New Delhi, IN
    ours
    Sagittarius 27°39′57.6″
    formula
    Sagittarius 27°39′59.2″
  • Sun Synthetic #0002
    0.05″
    2025-01-27 19:05 · Chennai, IN
    ours
    Aquarius 07°51′56.7″
    JPL
    Aquarius 07°51′56.6″
  • Moon Synthetic #0002
    0.08″
    2025-01-27 19:05 · Chennai, IN
    ours
    Capricorn 13°05′35.3″
    JPL
    Capricorn 13°05′35.2″
  • Mars Synthetic #0002
    0.07″
    2025-01-27 19:05 · Chennai, IN
    ours
    Cancer 21°52′41.3″
    JPL
    Cancer 21°52′41.4″
  • Mercury Synthetic #0002
    0.09″
    2025-01-27 19:05 · Chennai, IN
    ours
    Capricorn 29°06′10.6″
    JPL
    Capricorn 29°06′10.5″
  • Jupiter Synthetic #0002
    0.35″
    2025-01-27 19:05 · Chennai, IN
    ours
    Gemini 11°23′01.5″
    JPL
    Gemini 11°23′01.1″

Rows 1 to 15 of 298 · real run

1 / 20

How big is the gap?

Every row in the table, grouped by its difference from the reference.

Rows by gap from the reference, in arc-seconds298 rows from 1,000 test charts. under 0.5″: 185 rows, 0.5 to 1″: 4 rows, 1 to 2″: 8 rows, 2 to 3″: 76 rows, over 3″: 25 rows.095190185under 0.5″40.5 to 1″81 to 2″762 to 3″25over 3″Gap (arc-seconds)Rows
298 rows from 1,000 test charts. Sun to Saturn are compared with NASA JPL; Rahu and Ketu with the mean node formula; lagna with the ascendant formula.

What we check

The same checks run for every test chart.

  • Sun to Saturn
    Against NASA JPL. Median 0.12″, 6683 of 7000 within 1″
  • Rahu and Ketu
    Mean node, against the standard mean node formula (JPL has no lunar nodes). Largest gap 0.28″
  • Lagna
    Against the ascendant formula with the apparent sidereal time (JPL has no ascendant). Median 0.12″, largest 9.77″

Run the comparison yourself.

Every input (date, time, place, time zone), our output, the ayanamsa, the reference and the gap, in one file. Check any row with your own software.

Download all test inputs and outputs (CSV)
FAQ

Questions about the tests.

Why Lahiri ayanamsa?

Lahiri (Chitrapaksha) is the ayanamsa adopted by the Indian government's calendar reform and the default in most Vedic software. Every answer from the API includes the ayanamsa it used.

Why does the table add nutation to the ayanamsa?

The ayanamsa field in the API answer is the mean Lahiri value. The positions themselves use the true value: the mean value plus the nutation in longitude, which swings by up to about 17″. To turn our sidereal positions into tropical ones, add both. The table shows the nutation for every row.

Mean node or true node for Rahu and Ketu?

The API returns the mean node. JPL does not publish lunar nodes, so we compare the mean node with the standard formula for it, on the true equinox of date. Ketu is always opposite Rahu.

Why are some gaps bigger than others?

The largest gaps are for the Moon and the lagna, which move fastest, mostly on dates after 2050. Future positions depend on a predicted correction for the Earth's rotation, and small differences in that prediction show up there first. The largest planet gap is 3.57″, the Moon on 2070-02-18.

How do you handle time zones?

Birth times are converted to UTC with the historical time zone rules for that place and date, including daylight saving. The reference uses the same UTC moment the API reports.

Why no real user data?

We never need it. Synthetic births cover more dates, places and time zones than real ones. No customer or end-user birth data is used in testing or published.

Want to see the endpoints these tests call? Read the docs.