Your AI assistant is guessing your kundli.
This one computes it.
Ask Claude or ChatGPT for a chart and it will invent a plausible one - wrong lagna, invented dasha dates, a nakshatra that was never there. Vedic Proof gives your assistant a real sidereal engine: lagna, nakshatra with pada, Vimshottari dasha, panchang and Ashta Kuta, computed to 9 published parameters you can read on /proof.
9 published parameters · 8 golden charts · 80 values regenerated live
hosted · no Docker · one URL · 14 days of unlimited calls, then $1.99/mo
- lagna
- Kumbha (Aquarius) 16° 22'
- chandra rasi
- Tula (Libra) 17° 55'
- surya rasi
- Meena (Pisces) 28° 04'
- nakshatra
- Swati pada 4
- tithi
- Dwitiya · Krishna (waning)
- mahadasha at birth
- Rahu until 1993
{
"ayanamsa": "Lahiri (Chitrapaksha)",
"houses": "whole sign (rasi bhava)",
"lagna": { "rasi": "Kumbha (Aquarius)", "deg": 16.37 },
"moon": { "rasi": "Tula (Libra)", "nakshatra": "Swati", "pada": 4 },
"tithi": "Dwitiya",
"dasha": { "lord": "Rahu", "ends": "1993-01-30" },
"tolerance": "arc-minutes, not arc-seconds"
}Regenerated by the live engine on every deploy. This is the shape your assistant receives.
Proof, not adjectives
8 golden charts · 80 published valuesEight hard cases - near midnight, inside a DST gap, pre-1970, southern hemisphere, high latitude, on a nakshatra boundary, on a dasha changeover, on the equator - regenerated by the live engine and shown with every parameter behind them. No competitor publishes a full pinned-parameters disclosure. That is the whole wedge.
- AyanamsaLahiri (Chitrapaksha), mean
- Node conventionMean Rahu / Ketu
- Time handlingIANA tzdata via the host Intl database, DST-aware
- House systemWhole sign (rasi bhava)
- Sunrise definitionDisc centre, standard refraction, spherical horizon at sea level
- Divisional chart formulasClassical cyclic division; D1, D2, D3, D7, D9, D10, D12
- Dasha year length365.2425 days (Gregorian mean year)
- Rounding and boundariesAssigned on unrounded longitude; displayed to the arc-minute
- Ephemeris source and versionBuilt-in analytic series - not Swiss Ephemeris
Tools exposed
6 total- get_vedic_kundlilagna, grahas, nakshatra, houses, vimshottari dashain: birth date, time, place
- get_panchangtithi, vara, nakshatra, yoga, karana, sunrise, sunsetin: date, place
- check_compatibilityAshta Kuta 36-point score with per-koota breakdownin: two birth records
- get_databankvargas, aspects, yogas, transits, dasha at a datein: dataset keys, birth data
- list_databankevery available dataset, with argument shapesin: -
- get_account_statustrial hours remaining, plan, tool-call countin: -
One page per computation
17 pages- Vedic Astrology API/vedic-astrology-api
- Kundli API/kundli-api
- Janam Kundli API/janam-kundli-api
- Birth Chart API/birth-chart-api
- Panchang API/panchang-api
- Muhurta API/muhurta-api
- Kundli Matching API/kundli-matching-api
- Ashta Kuta API/ashta-kuta-api
- Guna Milan API/guna-milan-api
- Dasha API/dasha-api
- Vimshottari Dasha API/vimshottari-dasha-api
- Divisional Charts API/divisional-charts-api
- Navamsa API/navamsa-api
- D9 Chart API/d9-chart-api
- Shadbala API/shadbala-api
- Ashtakavarga API/ashtakavarga-api
- Yoga API/yoga-api
Questions
- What is Vedic Proof?
- A hosted sidereal (Jyotisha) computation engine your AI assistant can call. Connect one URL in Claude, ChatGPT, Cursor or any MCP client and the assistant returns a computed Janma Kundli, panchang, Vimshottari dasha and Ashta Kuta score instead of an invented one.
- How is this different from just asking Claude for a chart?
- A language model has no ephemeris. Asked for a kundli it produces a plausible-looking answer: a wrong lagna, dasha dates that were never computed, a nakshatra that does not belong to that birth. Vedic Proof computes the chart and returns the numbers, with the parameters behind them published.
- Which ayanamsa and house system do you use?
- Lahiri (Chitrapaksha) ayanamsa and whole sign (rasi bhava) houses. Both are pinned and published, along with seven other choices that move a chart, on the proof page.
- What does it not do yet?
- There is no REST interface yet - MCP only. One ayanamsa, seven vargas, arc-minute precision, no KP system. Those limits are listed in full on the pricing page rather than hidden.
- What does it cost?
- 14 days of unlimited calls with no card, then $1.99 a month with no per-call fee.
Connecting
- step 1
Create an account
Email or Google. The 14-day free trial starts on confirmation.
- step 2
Paste one URL as a connector
Claude: Settings → Connectors → Add custom. ChatGPT: developer-mode connector, auth type OAuth.
- step 3
Approve access once
Sign in on the consent screen; the tools appear in your client.