Panchang
Daily and event-oriented calendrical data for regional experiences.
Explore Panchang →Developer infrastructure
Vedic astrology API, with the calculation choices in view.
Use structured Jyotish outputs to build apps, calendars, reporting workflows and decision tools. Start with the endpoint family your product needs, then specify the provider and conventions that make results reproducible.
Documented scope
Broad coverage, explicit inputs.
The current source portal documents 107 endpoints in 16 families. Commercial access, credentials and live URL details are confirmed directly for a new TKR integration; this site does not publish an unverified API contract.
Kundli
Birth-chart calculations and structured planetary information.
Explore Kundli →Muhurat & timing
Timing components for planning experiences, with conventions made clear.
Ask about coverage →Compatibility
Matching workflows with structured calculation outputs for your own presentation layer.
Ask about coverage →Integration posture
A clear separation between astronomy and Jyotish rules.
Ephemeris choice is a technical input. Regional and interpretive conventions are separate choices. Exposing them is how a team can investigate differences instead of guessing why two charts disagree.
- Provider selection: documented values include
tkr_formulaandde440. - Regional choice: the source snapshot lists 13 named options.
- Response locale: 11 accepted values, separate from calculation rules.
InputDate · time · place
ConfigurationProvider · ayanamsa · region
OutputStructured calculation data
Buyer questions
Check these before implementation.
Which calculation provider?
Pick Formula-Lite or DE440 according to the dates, accuracy needs and deployment model your product actually requires.
Compare options →Which regional convention?
Do not assume a single India-wide Panchang rule. Declare and test the convention for your audience.
Regional scope →Which commercial model?
Hosted calls, redistribution and native runtime licensing are not interchangeable. Get the intended use in writing.
Licensing questions →Ready to evaluate the API?
Email your use case, expected volume, target markets and calculation requirements.