Build with the Kendraya Engine API.
The calculations behind Kendraya, available to your application through a hosted API. Send a request and receive a versioned result, without installing astronomical datasets or maintaining a calculation engine.
Invite-only API preview. Usage-based pricing is planned; paid plans and automatic billing are not available yet.
Your application. Our calculation service.
Call the API from your server using a private key. Kendraya runs the calculation and returns JSON with the selected conventions and engine version. The implementation and orbital dataset stay on our servers. No downloadable engine or offline data package is offered.
| Operation | Result |
|---|---|
positions | Sun through Pluto, mean or true lunar nodes, motion and retrograde state; tropical or sidereal coordinates |
chart | A birth chart with houses, lunar mansion, traditional periods and recorded calculation settings |
| Date coverage | 1900–2100 for planetary positions; birth dates up to today |
| Access | Private API key, per-key request limits and a versioned JSON contract |
One request to get started.
After receiving a preview key, send a JSON request to POST /api/v1/engine. Keep your key on your server, never in a browser or mobile app bundle.
curl https://kendraya.com/api/v1/engine \
-H "Authorization: Bearer $KENDRAYA_API_KEY" \
-H "Content-Type: application/json" \
--data '{
"schema": "kendraya-engine-request-1",
"operation": "positions",
"at": "2000-01-01T12:00:00Z",
"zodiac": "sidereal",
"bodies": ["Sun", "Moon", "Venus"],
"settings": { "ayanamsa": "lahiri", "nodeMode": "mean" }
}'The response includes calculated positions, motion and provenance. Current engine version: kendraya-jpl-2. Birth details belong only in the request body. This service does not save or log request bodies or calculation results, and responses are not cached.
Requests are limited to 8 KiB. Invalid keys return 401, invalid calculation input returns 400, and a request limit returns 429 with a Retry-After header. A successful response includes a request ID and the remaining per-minute allowance. Preview limits reset on service restart and are not billable usage records.
Pay for the calculations you use.
The planned commercial model is usage-based API access. Prices, included usage and any limits will be agreed before paid access begins. There is no checkout or automatic charge during this preview.
Personal transits, chart comparison, birth-time exploration and local rise/set calculations already power parts of Kendraya or its internal tooling. They are outside this initial API contract; request access if your product needs them.
Clear conventions and tested limits.
Positions come from the unmodified NASA/JPL DE440s ephemeris, bundled on Kendraya’s servers with a checked fingerprint and read by Kendraya’s own file reader, so a request never depends on an outside data service. In the audit of 3 October 2026, 2,560 apparent geocentric longitude and latitude pairs from 1900 to 2100 agreed with NASA/JPL Horizons to within 0.757 arcseconds. The method, results and limits and a JSON audit summary are public. NASA and JPL do not endorse Kendraya.
Sampled checks do not establish universal accuracy or the predictive validity of astrology. Traditional interpretations remain distinct from astronomical calculations.
The current engine uses IAU 1976/1980 frames and geocentric positions. Mars through Pluto use planetary-system centres of mass. Wider dates, additional house systems, asteroids and local eclipse visibility need further implementation and independent validation.
Kendraya’s implementation is proprietary. Third-party scientific data and routines retain their own rights and attribution, recorded in the calculation notices. Try a birth chart to experience the engine.