Skip to content
96Astro API
Get API Key

Compare

96Astro API vs Prokerala

Prokerala's astrology API publishes a complete OpenAPI 3.0 description with 113 operations: Vedic horoscope and charts, daily panchang, marriage matching with strong South Indian coverage, Pythagorean and Chaldean numerology, Western charts and a calendar endpoint. It has a permanent free plan. Facts checked 19 October 2026 Endpoints checked 27 October 2026 Operated by Ennexa Technologies Pvt. Ltd. (api.prokerala.com)
100%mapped

Their endpoints with an equivalent here

Of the 53 endpoint groups we mapped:

  • Dedicated capability32
  • Section of a capability4
  • Related, differs17
  • No equivalent yet0
See the mapping

Side by side

At a glance

Documented operations
Prokerala113 (published OpenAPI)
96Astro API643 capabilities (643 generally available)
Ayanamsha options
Prokerala4 sidereal (Lahiri, Raman, KP, KP new) plus tropical
96Astro API51 sidereal ayanamshas plus tropical
Request style
ProkeralaGET with query parameters; coordinates as "lat,lng", ISO date-time with offset
96Astro APIPOST JSON: ISO 8601 local date-time with an IANA time zone
Authentication
ProkeralaOAuth2 client credentials (token valid one hour)
96Astro APIAPI key in a header; no token exchange
OpenAPI description
ProkeralaOpenAPI 3.0
96Astro APIOpenAPI 3.1
Webhooks and background jobs
ProkeralaNot documented; PDF reports returned directly
96Astro APISigned webhooks; PDF and audio reports as background jobs
Free allowance
Prokerala5,000 credits a month, permanently
96Astro API14-day trial, then Spark, our free plan (1,000 live credits a month)
KP, Jaimini, Lal Kitab, Varshaphal, muhurta finder
ProkeralaKP charts and significators; the others are not in their spec
96Astro APIAll, including KP horary

What Prokerala offers that we do not

  • A larger permanent free allowance (5,000 credits a month against our 1,000).
  • 32 Pythagorean numerology operations and 5 Chaldean ones (ours: Vedic numerology and Chaldean name numbers).

The same everywhere in the 96Astro API

  • One request shape for every chart capability: a local date-time with its IANA time zone, latitude and longitude, and an optional ayanamsha (Lahiri by default) and node.
  • Every response carries a request_id, and errors use one JSON shape with a stable code (see errors).
  • Positions come from the Swiss Ephemeris; the accuracy page publishes our comparison with NASA JPL Horizons.

Sources

Their figures are as published on the dates above; we did not call their API. Prokerala is a trademark of its owner. If something here is out of date, tell us and we will correct it.