Swiss Ephemeris. Local compute.
Verified against JHora and Drik.
Drop-in replacement for VedicAstroAPI — same endpoints, same parameters, change one environment variable.160 of 180 divisional placements match JHora 8.x (June 2026 reference chart). Panchang checked against Drik Panchang: festival and fasting dates match, tithi times within 2 minutes.
Every day your app runs on an unverified Vedic astrology API is a day a wrong dasha date or wrong divisional sign reaches your users. Accuracy is not a feature — it is the product.
No credit card. 7-day free trial. Live in 60 seconds.
One environment variable. That's the entire migration.
Same endpoint paths. Same parameter names. Same response structure. Your code stays identical.
Vedic astrology API accuracy —
published benchmarks you can verify yourself.
Any API can claim accuracy. We show the methodology, the reference software, and the exact numbers. Run the same test yourself in 5 minutes.
Divisional Charts vs JHora 8.x
All 20 divisional charts (D1–D60) × 9 planets compared with Jagannatha Hora 8.x on the June 2026 reference chart: 160 of 180 sign placements match. The other 20 come from conventions (JHora puts Ketu opposite Rahu in every varga; we use the Parashari D2 hora scheme) and 3 Sun placements within seconds of arc of a varga boundary.
Key fix: Rahu uses mean node (SE_MEAN_NODE), matching JHora. Ketu = Rahu divisional sign + 6, per BPHS. D24 Siddhamsha: odd signs from Leo, even from Cancer.
Panchang vs DrikPanchang
Tithi, Nakshatra, Yoga, Karana, Choghadiya, Rahu Kaal, Yamagandam, Gulika — checked against DrikPanchang.com. Sunrise, sunset and Rahu Kaal within 1 minute across timezones including Birmingham, Mumbai, New York, Sydney; tithi times within 2 minutes.
Sunrise/sunset uses the Swiss Ephemeris's swe_rise_trans() directly — not Spencer (1971) approximation which gives ±15 min error.
Full Audit — June 2026
Every single endpoint tested in a live audit against the golden reference chart. All 128 return 200 with correct data. Auth (401 bad key, 400 missing params) verified on every endpoint.
Audit scope: horoscope, dashas, doshas, panchang, matching, predictions, utilities, AI layer. Results in BUILD-LOG.md on GitHub.
Three features no other Vedic astrology API offers.
Built from scratch. Not available anywhere else.
AI Narrative Layer (BYOLLM)
Full chart interpretations, dasha period stories, transit forecasts, and synastry reports in human-quality language — streamed in real time from your own connected AI provider. No competitor has this.
MCP Server
Query any of the 161 endpoints your plan includes directly from Claude Desktop, Cursor, or any MCP-compatible AI tool. Ask "what is the dasha for this birth data?" and get real Swiss Ephemeris output inline.
Embeddable AI Chat Widget
Drop one script tag. Your users get a live Vedic astrology AI assistant powered by real chart data — not generic horoscope text. Works on any website.
VedIntel™ AstroAPI vs VedicAstroAPI — full feature comparison
We note every category honestly — including where we are equal.
| Feature | VedIntel™ AstroAPI | VedicAstroAPI |
|---|---|---|
| Computation engine | ✓ Swiss Ephemeris — 100% local | External API dependency |
| Third-party dependency | ✓ None — zero downtime risk | Yes — their uptime = your uptime |
| Divisional chart accuracy | ✓ 160/180 placements match JHora 8.x | Not published |
| Panchang accuracy | ✓ Drik-checked: dates match, tithi within 2 min | Not published |
| AI interpretation | ✓ AI narratives (BYOLLM) — live | None |
| Code generation | ✓ Component Builder — real, verified integration code (BYOLLM) | None |
| Natal chart cache | ✓ Permanent (Supabase) — 10ms on cache hit | Not documented |
| Endpoint count | ✓ 161 endpoints — same set on every paid plan | 100+ (split across 3 plan types) |
| Billing model | ✓ One plan — all endpoints included | Separate plans for Vedic/Western/Tarot |
| Drop-in compatibility | ✓ /v3-json/* rewrites live | N/A (incumbent) |
| Divisional charts | ✓ D1–D60, BPHS-correct per-chart formulas | D1–D60 (formula undisclosed) |
| Dasha systems | = Vimshottari + Yogini + Char | = Vimshottari + Yogini + Char |
| MCP server | ✓ Live — npm @vedintelastroapi/mcp-server | None |
| WordPress plugin | ✓ Live — wordpress.org | None |
| Languages | ✓ 23 languages | Limited |
| Free trial | ✓ 500 calls, 7 days — 142 of 161 endpoints (AI features, PDF reports and Component Builder need a paid plan; 8 advanced-technique endpoints need Starter or above) | 14-day trial, ~20-30 essential endpoints |
Vedic astrology API pricing — VedIntel™ vs VedicAstroAPI
Every paid VedIntel™ AstroAPI plan includes the same 161 endpoints — no plan splitting. AI narratives (BYOLLM) are included from Developer plan and above.
| Plan | VedIntel™ AstroAPI | VedicAstroAPI |
|---|---|---|
| Free | ✓ ₹0 — 500 calls, 7 days, 142 of 161 endpoints | 14-day trial, ~20-30 essential endpoints |
| Developer | ✓ ₹799/mo — 75,000 calls/mo | No equivalent |
| Starter | ✓ ₹2,499/mo — 6,20,000 calls | ₹1,499/mo — fewer endpoints |
| Professional | ✓ ₹12,500/mo — 19,00,000 calls | ₹4,999/mo — 5,00,000 calls |
| Enterprise | ✓ Contact Us — Unlimited | ₹14,999/mo — 20,00,000 calls (not unlimited) |
Prices sourced from public pricing pages. Subject to change.
How to switch from VedicAstroAPI — 15-minute migration guide
Step by step. No surprises.
Sign up and get your API key
2 minCreate a free account at vedintelastroapi.com/auth/signup. Your key is live immediately — no waitlist, no credit card required.
Change one environment variable
1 minSet VEDIC_API_BASE to https://vedintelastroapi.com/v3-json — our /v3-json/* rewrites are live. Nothing else changes.
Run your existing test suite
5 minSame parameter names (api_key, dob, tob, lat, lon, tz). Same response structure. Your tests pass unchanged.
Verify accuracy against JHora
5 minReference: dob=27/08/1976, tob=10:05, lat=12.976794, lon=77.590082, tz=5.5 → Libra ascendant, Moon in Virgo. 160 of 180 divisional placements match JHora 8.x.
Switch billing
2 minCancel your old subscription. Pick the VedIntel™ AstroAPI plan that matches your call volume — same endpoints, more accuracy, lower price at every tier.
Vedic astrology API — frequently asked questions
How do I know the divisional charts are accurate?
We verified 180 data points — all 20 divisional charts × 9 planets — against JHora 8.x, the industry-standard Vedic astrology desktop software. The ground truth is saved at tests/reference-divisional-charts.json in our public GitHub repo. Run the same check yourself in 5 minutes.
Does it use the exact same endpoint paths as VedicAstroAPI?
Yes. We support /v3-json/* via Next.js rewrites pointing to our /api/v1/* handlers. Change VEDIC_API_BASE and every endpoint resolves identically. No code changes required.
Why does the local Swiss Ephemeris matter?
If an external computation service has downtime, your app goes down too — regardless of your own infrastructure. Our Swiss Ephemeris runs inside our own Next.js process. No HTTP call, no external dependency, no single point of failure outside your control.
Is the Panchang accurate for international timezones?
Yes. Sunrise and sunset use the Swiss Ephemeris's swe_rise_trans() directly — not the Spencer (1971) approximation formula which gives ±15 minute errors. Verified against DrikPanchang.com for Birmingham (BST), Mumbai (IST), New York (EDT), and more.
Can I try before I pay?
Yes. Free trial: 500 API calls over 7 days, 142 of 161 endpoints (AI features, PDF reports and Component Builder need a paid plan; 8 advanced-technique endpoints need Starter or above), no credit card. Your key is live in under 60 seconds.
What is the AI interpretation layer?
Endpoints under /api/v1/ai/* send structured Vedic chart data to your own connected AI provider (BYOLLM — OpenAI or Anthropic) and return written readings — full chart interpretations, dasha period stories, transit forecasts, and compatibility reports in fluent natural language. No competitor has this. Included from Developer plan and above.
Do I need separate plans for Vedic, Western, and Tarot endpoints?
No. Every VedIntel™ AstroAPI plan includes the same 161 endpoints — Vedic, panchang, matching, predictions, Western, Tarot, all in one plan. AI narratives (BYOLLM) are included from Developer plan and above too.
Are natal charts cached?
Natal charts are permanently cached in Supabase using SHA256 of birth data. The second call for the same birth data returns from cache in under 10ms — never recomputed. This also means your call balance is not consumed on cache hits.
Your users deserve accurate data.
Start in 60 seconds.
500 free calls, 7-day trial. 142 of 161 endpoints unlocked. Swiss Ephemeris accuracy from the first call. No credit card. No commitment.
Questions? Contact us — we reply in under 4 hours.