Occult API vs VedAstro: 299 named endpoints vs a handful of categories
Kalachakra dasha, the Tamil calendar, saptashalaka chakras — what happens in month two, when your API has no name for what you need.
Mridul KabraThe team behind the API2 min read
A handful of broad endpoints will get a simple app running. It is the second month that hurts — when a feature needs Kalachakra dasha, or the Tamil calendar, or a saptashalaka chakra, and the API simply has no name for it.
299 named endpoints
Occult API does not hand you a few large objects to dig through. It gives you 299 separate, documented endpoints, each with its own schema and its own verified response:
- Muhurta — choghadiya, planetary hora, rahu kaal, abhijit, panchak, durmuhurat, brahma muhurat, amrit kaal, auspicious and inauspicious windows.
- Dashas — twelve named systems, each its own endpoint: Vimshottari, Yogini, Ashtottari, Shodashottari, Kalachakra, Chara, Narayana, Sudasa and more.
- Calendars — eleven regional systems with tithi-based festival dates and exact timestamps.
- Classical technique — ashtakavarga with prastara and sodhana, Tajika annual charts, sahams, chara karakas, shadbala, ishta-kashta phala, the chakra family.
- Beyond Jyotish — Hellenistic dignities and almuten, Chinese BaZi and four pillars, astrocartography lines and parans, eclipse visibility paths, 735 fixed stars, tarot.
A named endpoint is not a cosmetic difference. It means the API can tell you what it is capable of, your IDE can autocomplete it, and an AI assistant reading the catalogue can find it without guessing.
48 ayanamsas with arcsecond correction
Exposed as a request field on every sidereal endpoint, with manual correction by degrees, minutes and seconds. If your users care which ayanamsa their chart uses — and serious Jyotish users do — you can simply let them pick.
Charts drawn for you
Set render: "svg" on the chart endpoint and get a finished North or South Indian diagram back, along with the geometry to render it natively yourself. Rendering a chart correctly is a real piece of work; this removes it.
Documentation that proves itself
Every endpoint shows a genuine response captured from a live server, and the playground sends the request from your browser before you spend a credit. Swiss Ephemeris with the full 105 MB data set, tested from 500–2999 AD, 65 ms median response with 69% of endpoints under 100 ms.
Pay for what you use, keep what you buy
Monthly or yearly plans with a monthly quota. One credit per successful call, failures free, and no tier that locks endpoints away.
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 VedAstro, side by side
Every figure in the VedAstro 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/vedastro.
| Feature | Occult APIRecommended | VedAstro |
|---|---|---|
| Free credits, and what they run onReal calls against the running API, not a sandbox with its own data. | 150 credits, live API | Free tier, 5 req/min |
| Median response timeMeasured across every published example, not a marketing round number. | 62 ms | <500 ms average |
| Ayanamsas, hand-correctablePick a tradition, then correct it by degree, minute and second. | 48, correctable | ~46, fixed list |
| 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.