Documentation
58 endpoints, 43 calculations, one envelope. Start with the quick start; come back to “why results differ” the first time a number surprises you.
The complete, generated list of endpoints with their request and response schemas is the API reference.
Getting started
- Quick start — Get a key and read your first kundli, in curl, Python or Node.
- Authentication — The three kinds of key, where each one may travel, and how origins are checked.
- Credits per API — What every API costs in credits, what is free, and what the limits do.
Getting it right
- Reports and horoscope — Lagna and nakshatra readings, a horoscope by sign, and the disclaimer.
- PDFs — Printable kundli, match, varshphal and monthly panchang PDFs, with your branding.
- Time zones — Wall clocks, offsets, historical zones, and the one field people get wrong.
- Why results differ — Ayanamsa, zone, sunrise convention and house system — the four usual suspects.
- Errors — Every error code, what causes it, and why none of them costs a credit.
Integrations
- Integrations overview — Every way to integrate, the 22 widgets in four groups with their credits, and which key runs where.
- Widgets — Twenty-two web components from one script tag: attributes, design, sign icons, the proxy and PDFs.
- WordPress plugin — The 22 widgets as blocks and shortcodes, with PDF downloads, a month cache and server rendering.
- Shopify — The widgets in a Shopify store with a Custom Liquid section, with examples.
- Wix — The widgets on a Wix site with an Embed HTML element, with examples.
- SDKs — Typed clients for TypeScript, Python, Dart and PHP: every route a method, PDFs, one error type.
- MCP for AI agents — The same calculations as tools for Claude, Cursor and any MCP client.
- Embed recipes — A panchang widget and an SVG chart in a page, with a publishable key.
A note on what this API is
It calculates. It does not predict, interpret or generate readings, and it never will — every endpoint returns numbers, positions, periods and the classical rules that fired, laid out for you or your users to read. What you build on top of that is yours.
Birth details are personal data. The API uses them to compute an answer and never stores them: no request body is logged, and the response cache is keyed on a hash of the normalised request. See the API privacy policy.