Occult API vs astrology-api.io: which Vedic astrology API to build on

If you are building anything Jyotish — panchang, kundli, muhurta, matchmaking, dashas — you want an API that was designed for it, not a Western astrology platform with a Vedic section bolted on the side.

That is the difference in one line. Here is what it means in practice.

48 ayanamsas, not one

Every sidereal calculation in Vedic astrology begins with a choice of ayanamsa, and Indian traditions genuinely disagree about which is correct. Ship Lahiri only and you quietly give the wrong answer to everyone who follows a different school.

Occult API exposes 48 — the Surya Siddhanta family, true Citra, true Revati, true Pushya, Raman, KP, Yukteshwar and the rest — and lets you hand-correct any of them by degrees, minutes and seconds. Your users pick their tradition and the maths follows.

244 endpoints, all of them named

Not "a chart endpoint with options". Separate, documented endpoints for choghadiya, rahu kaal, abhijit muhurat, planetary hora, panchak, tarabala, chandrabala, twelve named dasha systems, ashtakavarga with prastara and sodhana, Tajika annual charts, sahams, the saptashalaka and panchashalaka chakras, and eleven regional calendars.

Each one has its own request schema and its own documented response, so you can find what you need and see exactly what comes back.

Charts you do not have to draw

Ask /api/astro/chart/ for render: "svg" and the response carries a finished North or South Indian diagram — plus the geometry behind it: every cell's polygon, its label position, and which planets sit in it.

Render our markup directly, or use the geometry to draw it natively in React, Canvas, Flutter or SwiftUI. Either way you skip the genuinely fiddly work of building a chart diagram from raw longitudes.

Pricing that does not punish a quiet month

Most astrology platforms sell access as a monthly subscription: an allowance that resets whether you used it or not, and tiers that decide which endpoints you are allowed to touch.

We sell prepaid credits. ₹2,200 for 21,050 credits — roughly ₹0.10 a call. One credit per successful call, whatever you ask for in it. Credits never expire. Failed requests are never charged. There is no tier that hides endpoints: every account reaches all 244.

Astrology traffic is seasonal. Credits that sit still until you need them fit that shape; a subscription that resets every month does not.

Speed you can check

A 65 ms median of server time, with 69% of endpoints answering in under 100 ms — measured across every published example, not a cherry-picked one. The slow endpoints are documented as slow, so you know before you integrate.

Positions you can audit

Swiss Ephemeris with the full 105 MB data set and 735 fixed stars, tested from 500–2999 AD. Our tropical positions agree with direct Swiss Ephemeris calls to within 0.00045°. You can reproduce that.

Start in the next five minutes

Create an account, generate a key, and send a real request from the playground before you write a line of code. Every endpoint in the reference shows a genuine response captured from a live server, so you can confirm the data is what you need first.

One credit per successful call. Failed requests cost nothing. Credits never expire.

See pricing  ·  Browse 244 endpoints  ·  Connect your AI assistant