Occult API vs astrology-api.io
Where Occult API and astrology-api.io differ on the things a Jyotish product runs into. Every astrology-api.io figure was read from its own public pages, and ours are measured from the running API.
Side by side
| Feature | Occult APIRecommended | astrology-api.io |
|---|---|---|
| Free credits, and what they run onReal calls against the running API, not a sandbox with its own data. | 150 credits, live API | 50 a month, resets |
| Median response timeMeasured across every published example, not a marketing round number. | 62 ms | ~300 ms |
| What one call costsA flat rate you can multiply: one credit a call, except PDF reports and AI chat. | 1 credit (PDF reports and AI chat: 25) | 1–100 credits |
| Every endpoint on every planNo tier decides which calculations you are allowed to call. | All 299 | Ultra+ only for premium |
| Ayanamsas, hand-correctablePick a tradition, then correct it by degree, minute and second. | 48, correctable | 12, fixed list |
| Failed requests chargedA 400 costs nothing here, so a bad integration cannot drain a balance. | Never | Doesn’t publish it |
On every Occult API account
No tier, no add-on, no minimum spend. These are the defaults.
Hand-correctable to the arcsecond
Each its own endpoint
Across eleven regional calendars
Thirty named systems, drillable
No tier hides an endpoint
Plus the layout geometry
A 400 costs you nothing
Every Occult API figure is measured from the running API, and republished on each deploy. The other platform's figures were read from its own public pricing and documentation pages between 15 September 2026 and 22 October 2026, and may have changed since. Where a cell says doesn’t publish it, that platform puts no figure on its public site — so there is nothing to compare against until you have signed up and measured it yourself. It does not mean the feature is missing, and we do not put a number there on its behalf.
The longer write-up
First published on our blog as 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.
299 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 you can work out in advance
Many astrology platforms put some endpoints behind higher tiers, so the plan you pick decides what you are allowed to call.
We sell monthly or yearly plans with a monthly quota. One credit per successful call, whatever you ask for in it. Failed requests are never charged. There is no tier that hides endpoints: every plan reaches all 299.
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. Cancel any time.
See pricing · Browse 299 endpoints · Connect your AI assistant
Check it yourself
Every endpoint is in the reference with a real response, and you can send a request from the browser before writing any code.