vedicproof
vedic proof · computation

Birth Chart API

What is a birth chart API?

A birth chart API converts birth data into the positions of the ascendant and planets at that moment. Vedic Proof returns them sidereally - tropical longitudes minus the Lahiri ayanamsa - with rasi, degree, nakshatra, pada, whole-sign house and retrograde state for each of the nine grahas.

Request

Tools are called over MCP, so an assistant connected to https://vedicproof.com/mcp invokes get_databank itself. The arguments it sends are:

tool · get_databank
{
  "date_of_birth": "1994-01-19",
  "time_of_birth": "05:22",
  "city": "Kochi",
  "country": "India",
  "datasets": [
    "chart",
    "planets",
    "houses"
  ]
}

Response

Every response carries a plain-language summary string plus structured data, and states the engine and ayanamsa it used. Abridged here for length.

result · json
{
  "requested": ["chart", "planets", "houses"],
  "data": {
    "chart": { "birth": { "utc": "1994-01-18T23:52:00.000Z", "julian_day": 2449371.494444 }, "yoga": "Shubha", "karana": "Balava" },
    "planets": [ /* nine grahas */ ],
    "houses": [ /* twelve whole-sign bhavas */ ]
  },
  "available_keys": ["chart", "planets", "houses", "vargas", "vimshottari_dasha", "dasha_at_date", "aspects", "yogas", "transits", "panchang"]
}

How is this calculated and verified?

These are the pinned parameters that affect this computation. The full disclosure, and the golden-chart corpus, live on /proof.

AyanamsaLahiri (Chitrapaksha), mean
Single supported system today, computed as a polynomial in Julian centuries from J2000 rather than read from a table. True-Chitra, KP-Newcomb and Raman are not offered; that is a limitation, not a default we are hiding.
Ephemeris source and versionBuilt-in analytic series - not Swiss Ephemeris
Sun from a truncated VSOP-style series, Moon from truncated ELP2000 terms, and Mercury through Saturn from JPL Keplerian elements. Accuracy is arc-minutes, not arc-seconds: a few arc-minutes for the Sun and Moon, up to roughly a tenth of a degree for the outer grahas. That is fine for rasi, nakshatra, pada, dasha and koota output and is not fine for arc-second work. Every API response carries the engine note stating this.
Rounding and boundariesAssigned on unrounded longitude; displayed to the arc-minute
Rasi, nakshatra and pada are assigned from the full-precision longitude before any rounding, so a graha at 29.9999° stays in its own rasi. Degrees are formatted d° mm' ss" for display only.

Common questions

Sidereal or tropical?
Sidereal. Every longitude in the response has the ayanamsa already subtracted, and the ayanamsa value used is returned alongside so you can reconstruct the tropical figure.
Why does my chart differ from another provider's?
Almost always one of nine parameters: ayanamsa variant, node convention, timezone handling, house system, sunrise definition, varga formula, dasha year length, boundary rounding, or ephemeris. Ours are all published on /proof.
Can I request only part of the chart?
Yes. get_databank takes a datasets array, so an app that only needs planets and vargas does not pay for the rest.

Connect this to Claude or ChatGPT with one URL: https://vedicproof.com/mcp. First 14 days unlimited and free, then $1.99/month.

claude setup →chatgpt setup →pricing →

Related computations

all computations in docs →