vedicproof
vedic proof · computation

Vedic Astrology API

What is a Vedic astrology API?

A Vedic astrology API turns birth details - date, time and place - into sidereal chart data a program can use: ascendant, graha positions, nakshatra, houses, divisional charts, dasha periods and compatibility scores. Vedic Proof serves those computations over the Model Context Protocol, so an assistant calls them directly and returns structured results.

Request

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

tool · get_vedic_kundli
{
  "date_of_birth": "1994-01-19",
  "time_of_birth": "05:22",
  "city": "Kochi",
  "country": "India"
}

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
{
  "summary": "Kochi, India, 1994-01-19 05:22 (UTC+5.5). Lagna Dhanu 12° 41' 08\". Chandra rasi Kumbha, janma nakshatra Shatabhisha pada 2. Surya rasi Makara. Tithi Ashtami (Krishna), Wednesday.",
  "ayanamsa": { "name": "Lahiri (Chitrapaksha)", "degrees": 23.8271 },
  "lagna": { "rasi": "Dhanu", "degree": "12° 41' 08\"", "nakshatra": "Purva Ashadha", "pada": 1, "lord": "Jupiter" },
  "planets": [ /* nine grahas with rasi, nakshatra, pada, house, retrograde */ ],
  "houses": [ /* whole-sign bhavas with rasi and lord */ ],
  "vimshottari_dasha": [ /* mahadashas with start and end dates */ ],
  "engine": "Computed by Vedic Proof's built-in sidereal engine (Lahiri ayanamsa, whole-sign houses)…"
}

Which computations are exposed?

ToolReturns
get_vedic_kundliFull Janma Kundli in one call
get_panchangTithi, vara, nakshatra, yoga, karana, sunrise, sunset
check_compatibilityAshta Kuta 36-point Guna Milan
get_databankAny subset: planets, houses, vargas, dashas, aspects, yogas, transits
list_databankThe dataset catalogue with argument shapes
get_account_statusTrial state, plan and call count

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.
House systemWhole sign (rasi bhava)
The lagna rasi is the first bhava in full; every graha's house is its rasi counted from the lagna rasi. Placidus, Sripati and KP cusps are not offered.
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.

Common questions

Is there a REST interface as well as MCP?
Not yet. Today Vedic Proof is MCP-only, over one URL and one account. A REST surface with an OpenAPI document is planned; until it exists we do not claim it.
Which ayanamsa does it use?
Lahiri (Chitrapaksha), mean. It is the only supported system today, and it is stated in every response rather than left implicit.
How accurate is it?
Arc-minutes, not arc-seconds: a few arc-minutes for Sun and Moon, up to about a tenth of a degree for outer grahas. That is sufficient for rasi, nakshatra, pada, dasha and koota output.

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 →