Kundli matching for a matrimony product
Gun Milan at list scale, with the cancellation rules intact.
A matrimony product needs two different things from an astrology API: a score good enough to rank a list of hundreds, and a breakdown good enough to show one couple why. AstroNode splits those into a batch endpoint and a detail endpoint that agree with each other, because both come from the same engine.
9 endpoints across 4 stages.
Worth knowing first
The half-marks rule is where implementations diverge
Most Ashtakoot implementations disagree on dosha cancellation, which is why two sites give the same couple different scores. Every koot here returns both the raw score and the post-cancellation score, so you can render whichever your audience expects - and explain the difference instead of hiding it.
Stage 1
Rank the list
Score a candidate against every profile in a shortlist in one call, then sort. This is the call that runs on a search-results page, so it is built for volume rather than depth.
Stage 2
Show one match in full
When someone opens a profile, they want the 36-point breakdown and the reasoning, not just a number.
Stage 3
Serve the South-Indian audience properly
Ashtakoot is the North-Indian convention. A Tamil or Telugu audience expects Porutham or Dashakoot, and showing them the wrong system reads as carelessness.
Stage 4
Sell the full report
A PDF is the natural paid upgrade on a free score. It is generated asynchronously, so queue it and poll.
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