Accuracy you can check yourself.

How we test

1. Tested against Swiss Ephemeris

   The engine is compared with Swiss Ephemeris 2.10.03 and its JPL-based files on 5,433 births: 5,000 random births from 1900 to 2100 between 60° S and 65° N, plus 433 edge cases near sign, nakshatra, pada, tithi and yoga boundaries and around clock changes.

2. A public golden corpus

   500 of those births with their inputs, our outputs, the reference values and the difference for each, free to download. Run the inputs against the API and compare.

3. Settings echoed in every response

   The meta block names the ayanamsha and its value, the node type, the timezone database, the BS table and Samiti override versions, and the engine version.

4. Birth-time sensitivity

   Set options.sensitivityMinutes and the response lists any lagna, D9 lagna, nakshatra or pada change inside that window, with the moment it changes.

5. Deterministic output

   The same input with the same engine and data versions returns byte-identical JSON. Dasha output never depends on the server clock.

6. Reviewed conventions

   Guna tables, dasha rules and choghadiya sequences are reviewed by a contracted jyotish reviewer before they ship.

Release tolerances

The target is what we aim for. A release that crosses a hard limit on any sample does not ship. Engine 0.1.0 stays inside every hard limit and meets every target except Mercury to Saturn, which reach 20.2″ against the 5″ target.