The Vedic calculation API.
One REST surface over the whole engine. Charts, dashas, divisional charts, yoga detection, doshas, strength, KP, panchang, muhurta, transits and citation-backed interpretation — all sidereal, all versioned, all deterministic.
01
Interface
One call, a whole chart
Post birth data, get the canonical chart object — positions, houses, nakshatra padas, dignities, divisional placements and the live dasha stack. Same input, same output, every time.
curl -X POST https://api.drikengine.com/v1/chart \
-H "Authorization: Bearer $DRIK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"birth_date": "1990-01-15",
"birth_time": "14:30:00",
"latitude": 28.6139,
"longitude": 77.2090,
"timezone": "Asia/Kolkata",
"ayanamsa": "lahiri"
}'{
"schema_version": "1.0",
"lagna": { "rashi": "Mesha", "rashi_number": 1, "degree": 14.72 },
"planets": {
"Sun": {
"rashi": "Makara", "degree": 22.34,
"nakshatra": "Shravana", "pada": 3,
"house": 10, "is_retrograde": false,
"dignity": "neutral",
"d9_rashi": "Vrishchika", "d10_rashi": "Mesha"
}
},
"dasha": {
"current_mahadasha": { "lord": "Jupiter", "start": "2019-03-14", "end": "2035-03-14" },
"current_antardasha": { "lord": "Saturn", "start": "2023-11-14", "end": "2026-07-14" }
}
}02
Surface
Forty-three endpoints
All under a single /v1 namespace. Sidereal throughout, ayanamsa selectable per request.
/v1/chart
/v1/positions
/v1/divisional-chart
/v1/navamsa
/v1/aspects
/v1/dasha/current
/v1/dasha/major
/v1/dasha/sub/{mahadasha}
/v1/dasha/narayana
/v1/dasha/shoola
/v1/yoga/detect
/v1/yoga/marriage
/v1/dosha/manglik
/v1/dosha/kalsarpa
/v1/dosha/sadhesati
/v1/strength/shadbala
/v1/strength/ashtakavarga
/v1/upagraha
/v1/upapada
/v1/transit
/v1/transit/monthly
/v1/panchang
/v1/muhurta/day
/v1/tajaka
/v1/marriage-timing
/v1/wealth-timing
/v1/health-timing
/v1/compatibility
/v1/kp/chart
/v1/kp/cusps
/v1/kp/planets
/v1/kp/ruling-planets
/v1/kp/ayanamsa
/v1/interpret
/v1/horoscope/daily
/v1/chat
/v1/reference/yoga
03
Pricing
Metered by call, nothing gated
No feature tiering — a starter key and an enterprise key reach the same engine and the same forty-three endpoints. You are paying for volume.
Starter
$49/mo
10,000 calls / mo
Build and validate. Full /v1 surface · Key management · Usage metering
Growth
Most used$299/mo
100,000 calls / mo
For a product in market. Full /v1 surface · Usage breakdown by endpoint · Self-serve billing
Scale
$999/mo
500,000 calls / mo
For volume traffic. Full /v1 surface · Higher rate limits · Self-serve billing
Enterprise
Custom
Unmetered
Dedicated and white-label. Volume pricing · White-label options · Negotiated SLA
chart.json is versioned and treated as a contract, not an implementation detail. A breaking change means a schema version bump, a migration path, and notice to every integrator before anything ships. That is the point of building on this rather than on a scraper.
Ship astrology you can stand behind.
Starter from $49/mo. The full endpoint surface at every tier.