Kundli API: Endpoints, Pricing and Build vs Buy (2026 Guide)

Harshita kalla· SEO Executive & Content Writer
Kundli API guide 2026: endpoints, pricing and build vs buy

A Kundli API takes a person's date, time and place of birth and returns a calculated Vedic birth chart as structured data, usually JSON, so your app can show planets, houses, dashas, doshas and matching scores without building its own calculation engine. Hosted plans start at about ₹1,000 a month in India and $19 a month in USD, and the Swiss Ephemeris is the main self-hosted option. Prices below were checked on each provider's own page on 12 November 2026.

Key facts

  • Inputs: date, exact time, latitude, longitude and time zone of birth.
  • Outputs: planetary positions, lagna, houses, Vimshottari dasha, divisional charts, doshas, yogas and matching.
  • Entry pricing checked 12 Nov 2026: FreeAstrologyAPI ₹1,000 per month for 50,000 requests; DivineAPI $19 for 100,000; RoxyAPI $39 for 50,000.
  • Free options: FreeAstrologyAPI (500 requests a day), Prokerala (5,000 credits a month), AstrologyAPI.com (150 credits on signup).
  • Self-hosting: the Swiss Ephemeris is free under the AGPL or available under a paid Professional License.

What a Kundli API Returns

Data blockWhat it containsTypical use in an app
Planetary positionsSidereal longitude, sign, nakshatra, house and retrograde status for each planetBirth chart screen, daily horoscope logic
Lagna and housesAscendant and the 12 housesChart diagram in North or South Indian style
Dasha periodsVimshottari mahadasha and antardasha timelineLife-period predictions and reports
Divisional chartsNavamsa (D9) and other varga charts, up to D60 on some plansMarriage and career analysis
Doshas and yogasMangal (Manglik) dosha, Kaal Sarp and yoga detectionRemedy content and consultation prompts
MatchingAshtakoota (Guna Milan) score out of 36 for two chartsMarriage compatibility reports

Sample Kundli API Request and Response

Field names differ by provider, but most Kundli endpoints follow this shape. The example is illustrative, not copied from any one vendor.

POST /v1/kundli
{
  "date": "1992-08-15",
  "time": "06:42",
  "latitude": 26.9124,
  "longitude": 75.7873,
  "timezone": "+05:30",
  "ayanamsa": "lahiri"
}

Response (trimmed)
{
  "lagna": { "sign": "Leo", "degree": 12.4 },
  "planets": [
    { "name": "Moon", "sign": "Taurus", "nakshatra": "Rohini", "house": 10, "retrograde": false }
  ],
  "dasha": { "current": "Venus-Saturn", "ends": "2027-03-02" },
  "doshas": { "manglik": false }
}

Kundli API Providers Compared (Checked 12 November 2026)

ProviderEntry planRequests includedFree optionNotes from the pricing page
FreeAstrologyAPI₹1,000 per month (Vedic Mercury)50,000 per month500 requests a dayHigher plans ₹3,500 and ₹6,500; prices exclude GST
DivineAPI$19 per month (Vedic Sampoorna)100,000 per month14-day trial, card requiredKundali Matching (Ashtakoot, Dashakoot) listed on the $149 Prakash plan
Prokerala$19 per month (Ruby)100,000 credits5,000 credits a monthCredits per request not stated on the pricing page
RoxyAPI$39 per month (Starter)50,000 per monthNot statedJyotish and KP kundli returned as one response; 1 request equals 1 unit
VedicAstroAPI₹1,499 per month (Vedic Limited)30,000 per monthNot stated100+ APIs on Vedic Complete plans; prices exclude GST
AstrologyAPI.com₹1,500 per month (Indian Astrology)Credit based150 credits on signupKundli, panchang, muhurta and matchmaking; 300+ endpoints
Swiss EphemerisFree (AGPL) or Professional LicenseUnlimited, self-hostedYes, under AGPLYou build Kundli rules, dashas and matching yourself

Cost per 1,000 Requests on Entry Plans

Calculated from the published entry plan price divided by the included requests. AstrologyAPI.com uses its own calculator example of ₹1,000 for 10,000 calls.

INR plans

FreeAstrologyAPI: ₹20
VedicAstroAPI: ₹50
AstrologyAPI.com: ₹100

USD plans

DivineAPI: $0.19
Prokerala (per 1,000 credits): $0.19
RoxyAPI: $0.78

Cost per request is only one factor. Endpoint coverage, language support, rate limits and support quality matter more for most apps, and higher tiers cut the unit cost sharply.

How a Kundli Request Works

  1. Collect birth details: date, exact time and place of birth.
  2. Resolve the place: convert it to latitude, longitude and the correct historical time zone, because daylight saving and offset rules have changed over the years.
  3. Call the API: send the date, time, coordinates, time zone and your chosen settings.
  4. Cache the result: store the chart against a hash of the birth details so a returning user never costs a second call.
  5. Render and interpret: draw the chart and generate text from the returned data.

Settings That Change the Answer

  • Ayanamsa: the offset between the tropical and sidereal zodiacs. Lahiri is the common default in India, and mixing settings gives different positions.
  • House system: whole sign and other systems place houses differently.
  • Time zone accuracy: a wrong offset for a past birth date shifts the ascendant.
  • Birth time precision: the ascendant changes roughly every two hours, so approximate birth times give unreliable lagna-based results.

Common Kundli API Problems and Fixes

ProblemLikely causeFix
Ascendant differs from another appDifferent ayanamsa or time zoneFix one ayanamsa and resolve historical time zones server-side
Costs grow faster than usersSame chart requested repeatedlyCache by a hash of birth details
HTTP 429 errors at peakPer-minute rate limit reachedQueue requests, cache, or move to a higher tier
Users enter a city the API cannot findWeak place searchUse the provider geo endpoint or your own place database
AI reading contradicts the chartLanguage model guessing positionsCalculate first, then pass verified chart data to the model

Build or Buy a Kundli API

SituationBetter route
MVP or early launchHosted API on an entry or free plan, with caching
India-first app needing Kundli, panchang and matchingAn INR plan that bundles all three
Millions of requests a monthCompare plan cost with self-hosting on the Swiss Ephemeris
Custom rules or proprietary reportsSelf-hosted engine, with license and engineering time budgeted

The Swiss Ephemeris is dual-licensed: you either place your project under the AGPL or buy the Professional License from Astrodienst, and you must choose before any public service goes live. For AI features, keep the chart calculation in the API or engine and let a language model write only the interpretation from the verified chart data.

How to Choose a Kundli API: Checklist

  • Does it cover every endpoint your screens need (Kundli, dasha, divisional charts, matching, panchang)?
  • Does it support the ayanamsa and chart style your users expect?
  • Are languages your users read supported?
  • What is the cost per request at your expected volume, including GST?
  • What are the rate limits, and what happens when you hit them?
  • Can you export or cache results under its terms?

Takeaway: choose a Kundli API by endpoint coverage and cost per request at your expected volume, cache every chart, and move calculations in-house only when volume justifies it.

Appic Softwares has built 12 astrology apps since 2018, including AstroGuide for Balaji Telefilms, and integrates Kundli, panchang and matching APIs through our astrology API integration services. Compare more providers in our astrological APIs guide, read the Panchang API guide and Kundli matching software guide, or talk to our astrology app development company team.

Frequently Asked Questions

What is a Kundli API?

A Kundli API is a web service that calculates a Vedic birth chart from birth date, time and place and returns planets, houses, dashas, doshas and matching data as JSON.

How much does a Kundli API cost?

On 12 November 2026, entry plans started at ₹1,000 per month (FreeAstrologyAPI, 50,000 requests) and $19 per month (DivineAPI, 100,000 requests). Check each pricing page for current rates and GST.

Is there a free Kundli API?

Yes, with limits. FreeAstrologyAPI offers 500 requests a day, Prokerala 5,000 credits a month, and AstrologyAPI.com 150 credits on signup.

Which Kundli API is best?

There is no single best one. Pick by endpoint coverage, languages, rate limits and cost per request at your volume, then test accuracy against charts you trust.

Can I build my own Kundli engine?

Yes, using the Swiss Ephemeris for planetary positions, then adding Kundli rules, dashas and matching yourself, under its AGPL or Professional License terms.

Which ayanamsa should I use?

Lahiri is the usual default for Indian Vedic charts. Use one setting consistently, because different ayanamsas give different planetary positions.

How accurate is a Kundli API?

Accuracy depends on the ephemeris, your settings and the quality of the birth time and time zone you send. Wrong time zone data is the most common cause of errors.

How do I reduce Kundli API costs?

Cache each chart against a hash of the birth details, request only the endpoints a screen needs, and move to a higher tier when volume grows.

Can AI generate a Kundli?

AI should not calculate planetary positions. Calculate the chart with an API or ephemeris engine, then use AI only to explain the verified result.

Sources

All pricing checked on 12 November 2026.