Occult API vs VedicAstroAPI
Where Occult API and VedicAstroAPI differ on the things a Jyotish product runs into. Every VedicAstroAPI figure was read from its own public pages, and ours are measured from the running API.
Side by side
| Feature | Occult APIRecommended | VedicAstroAPI |
|---|---|---|
| Free credits, and what they run onReal calls against the running API, not a sandbox with its own data. | 150 credits, live API | 14-day trial |
| Median response timeMeasured across every published example, not a marketing round number. | 62 ms | Doesn’t publish it |
| Every endpoint on every planNo tier decides which calculations you are allowed to call. | All 299 | Tiered |
| Ayanamsas, hand-correctablePick a tradition, then correct it by degree, minute and second. | 48, correctable | Doesn’t publish it |
| 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 VedicAstroAPI: every endpoint on every account.
Two Vedic-first APIs, one straightforward question: which one lets you build without hitting a wall six weeks in?
Every endpoint, on every account
It is common for astrology APIs to tier access — a cheaper plan that reaches "essential" endpoints, a dearer one that unlocks the rest. You discover the boundary at the worst possible moment, when a feature you have already designed turns out to sit on the other side of it.
Occult API has no such line. Every plan reaches all 299 endpoints at the same flat one credit per successful call. There is no plan on which an endpoint is invisible to you, and nothing to upgrade in order to finish what you started.
A quota you can plan around
Monthly plans come with allowances that end when the billing period does. Unused calls simply vanish.
Ours is a monthly or yearly plan with a monthly quota, and the smallest plan reaches every endpoint: you upgrade to make more calls, never to unlock a calculation. Failed requests are never charged either.
Regional calendars as real endpoints
Bengali, Tamil, Malayalam, Nepali, Gujarati, Marathi, Kannada, Telugu, Assamese, Odia and ISKCON each have their own endpoint, returning tithi-based festival dates with exact begin and end timestamps for the whole year. Not a generic list with a language flag on it — the actual regional reckoning.
48 ayanamsas, and manual correction
Indian users argue about ayanamsa, and they are right to: the tradition genuinely disagrees with itself. Rather than pick a side, we expose 48 — Lahiri, Raman, KP, Yukteshwar, the Surya Siddhanta family, true Citra, true Revati, true Pushya — plus manual correction by degrees, minutes and seconds. Let your users choose and stop fielding the complaint.
Depth where Jyotish products actually need it
- Muhurta split into choghadiya, planetary hora, rahu kaal, abhijit and panchak — each its own endpoint.
- Twelve named dasha systems, not one endpoint with a string parameter.
- Ashtakavarga including prastara and sodhana, Tajika annual charts, sahams, and the saptashalaka and panchashalaka chakras as structured data.
- Chart SVG rendering with the layout geometry attached, so you never draw a North Indian diagram by hand.
Verify before you commit
Every endpoint's documentation shows a real captured response, and the playground sends the request live from your browser. Swiss Ephemeris, 105 MB data set, 735 fixed stars, 500–2999 AD, 65 ms median.
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.