Hosted Vedic astrology API
Structured endpoints across Panchang, Kundli, Muhurat, matching and more. Published provider choices make the calculation path visible in each request.
Explore API capabilities →Astrology infrastructure for buildersAncient timing.
Ancient timing.
Modern engine.
Build serious Vedic astrology products with a hosted API and an independent calculation-engine path. Panchang, Kundli, regional conventions and planetary positions—designed for developers who need the rules made explicit.
TKR / Engine architecture
TKR
Formula-LiteVSOP87-based calculation
JPL DE440Precision ephemeris option
107documented API endpoints
16documented API families
2named ephemeris providers
1technical foundation to evaluate
One platform, two delivery paths
Access the calculation layer the way your product needs.
The hosted API serves web and server-side integrations. Native offline use is handled as a separate licensing discussion, with target platform, size, validation and support terms confirmed before purchase.
Offline engine licensing
Discuss local-first, native calculation for mobile or embedded products. Availability and binary deliverables are scoped per agreement; this is not a public SDK download.
Discuss native deployment →What you can build
From daily Panchang to full Jyotish workflows.
Useful product pages, clear calculations and regional choices matter more than another generic horoscope feed.
Panchang & calendar
Tithi, nakshatra, yoga, karana and day-level timing for calendars and ritual products.
Panchang API →Kundli & charts
Planetary positions, birth-chart building blocks, divisional-chart and timing workflows.
Kundli API →Ephemeris choice
Compare the Formula-Lite calculation path with the JPL DE440 kernel-backed path.
Engine options →Enterprise licensing
Evaluate integration, commercial use, regional scope and a support model tailored to your deployment.
Licensing enquiry →Calculation transparency
Know which engine answered.
A calculation should be reproducible, not a black box. The documented API requires an explicit provider selection; the selected provider is returned with the result. That makes technical review and regression testing easier.
- Formula-Lite: an in-house implementation using VSOP87 planetary-series coefficients.
- DE440: an in-house reader for NASA JPL's DE440 kernel.
- No silent fallback: provider and convention choices are part of the documented request.
Product inputDate · place · convention
Provider choicetkr_formula / de440
Structured resultProvider identified
Built for Indian depth
Regional conventions are a product requirement, not an afterthought.
One “Indian calendar” setting cannot describe every Panchang tradition. The current documented platform exposes named regional choices and separate locale values, so integrators can define exactly what their users receive.
Explore regional Panchang →Named regional choices
Documented regional parameters—not a claim that every local tradition is identical or fully covered.
Accepted response locales
Published language values are separate from calculation conventions and UI translations.
Technical buyer checklist
Evaluate the engine before you commit.
Verify inputs
Ask for the supported date range, location format, ayanamsa, regional conventions and provider identifier required for your use case.
Technical notes →Compare outputs
Use your own reference cases to review planetary positions and calendrical edge cases before integration.
Calculation options →Scope a licence
Hosted API, local runtime and redistribution have different terms. Request a written scope before shipping.
Talk licensing →Building a Panchang or Kundli product?
Tell us your platform, traffic and calculation requirements. We will map the right evaluation path.