Occult API vs VedicAstroAPI: every endpoint on every account
No tier hides an endpoint, failed calls are never charged, and 11 regional calendars plus 48 ayanamsas come as standard.
Mridul KabraThe team behind the API2 min read
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
Occult API vs VedicAstroAPI, side by side
Every figure in the VedicAstroAPI column was read from their own public pages. Ours are measured from the running API. The current comparison, kept up to date, is at occultapi.com/vs/vedicastroapi.
| 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 |
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.
Build this yourself
Every endpoint mentioned here is in the reference, and you can send a real request from the browser before writing any code.