Tooling for practising astrologers
The calculations, so you can build the consultation.
A working astrologer does not need an app to tell them what a chart means - they need the chart computed correctly, fast, and in every divisional and dasha system they actually use. That is arithmetic, it is where software beats hand calculation, and it is the part you should not be writing yourself.
14 endpoints across 4 stages.
Worth knowing first
Name the convention on every output
Ayanamsa and house system choices change a chart materially, and a professional will check. Every response carries the engine version and the convention used in its `meta` block, so a printed chart can say which it is - which is also what makes two runs reproducible.
Stage 1
The chart stack
D1 plus the divisional charts. Varga can return one division or all sixteen in a single call.
Stage 2
Strength and timing
Ashtakavarga and the dasha systems are the two things most worth automating - both are pure bookkeeping and both are easy to get subtly wrong by hand.
Stage 3
Other traditions, same key
KP and Lal Kitab are separate systems with their own conventions, not skins over the Vedic chart.
Stage 4
What the client takes home
Remedies are what a consultation ends on, and an annual reading is the natural repeat appointment.
Start
One key covers all of it
Every endpoint above takes the same bearer token and returns the same envelope. Free tier covers 1,000 requests / month. Pick your language in the quickstarts, or run any of these without a key in the playground.
Other use cases