Occult API vs Vedika: exact calculations under your AI
An AI reading is only as good as the chart beneath it. Deterministic, auditable Jyotish computation you can build your own product on.
Mridul KabraThe team behind the API2 min read
An AI that writes you a paragraph about your chart is only as good as the chart underneath it. If the numbers are approximate, the prose is confident nonsense.
Occult API is the layer underneath: exact, deterministic, auditable calculation that you build your own product on top of.
Computed, not generated
Every one of our 299 endpoints returns computed values — longitudes, timestamps, tithis, house cusps, dasha boundaries. The same request returns the same answer every time, and you can check it against an ephemeris. Nothing is invented, nothing drifts between calls.
That predictability is what you need when a user is going to act on the answer: book a muhurta, match a horoscope, plan a ceremony.
One flat price, published in full
Monthly or yearly plans with a monthly quota. One credit per successful call whatever the endpoint, failed requests free, no seat charges, no per-query rate card to model.
You can work out your bill on the back of an envelope before you integrate — and all 299 endpoints are available on every plan at that same rate.
Your AI assistant, connected properly
Our MCP server plugs Claude, Cursor or any MCP-compatible assistant straight into the API. Five tools, three of them free: search the whole catalogue, read any endpoint's exact request schema, and check your balance without spending a credit. Only the actual calculation costs anything.
So your assistant can explore 299 endpoints, learn the real request format, and then make one correct call — instead of guessing at field names and burning your budget on retries.
Jyotish depth, not a veneer
- 48 ayanamsas with arcsecond correction.
- Twelve named dasha systems, each its own endpoint.
- Muhurta broken out into choghadiya, hora, rahu kaal, abhijit and panchak.
- Eleven regional calendars with tithi-based festival timings.
- Ashtakavarga, Tajika, sahams, chakras, astrocartography, eclipse visibility paths.
- Chart SVG rendering with layout geometry attached.
Accuracy you can reproduce
Swiss Ephemeris with the full 105 MB data set and 735 fixed stars, tested from 500–2999 AD. Tropical positions agree with direct Swiss Ephemeris calls to within 0.00045°. Median response 65 ms.
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 309endpoints · Connect your AI assistant
Occult API vs Vedika, side by side
Every figure in the Vedika 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/vedika.
| Feature | Occult APIRecommended | Vedika |
|---|---|---|
| Free credits, and what they run onReal calls against the running API, not a sandbox with its own data. | 150 credits, live API | 130+ mock endpoints |
| Median response timeMeasured across every published example, not a marketing round number. | 62 ms | 200–800 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) | $0.01–$0.05 |
| Ayanamsas, hand-correctablePick a tradition, then correct it by degree, minute and second. | 48, correctable | 4, 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.