Does the chart payload include classical Shadbala fields?

Yes. Every planet in the chart returns the six classical Shadbala components: Sthana Bala (positional), Dig Bala (directional), Kala Bala (temporal), Cheshta Bala (motional), Naisargika Bala (natural), Drik Bala (aspectual). Each is broken out into sub-parts and the Shadbala Pinda total is included. Ishta and Kashta phala are derived from these and returned alongside. So you can show users not just that a planet is weak, but exactly which component dragged it down. Prokerala and VedicRishi typically return a single Shadbala total or skip it entirely.

Does the API return D60 deity and Krura/Saumya nature?

Yes. The Shashtiamsa (D60) divides each sign into 60 parts of 0 degree 30 minute each. Every one of those 60 has a Parashara deity (Ghora, Rakshasa, Deva, Kubera, Yaksha, Kinnara and others) and a classical nature - Krura (harsh) or Saumya (gentle). The chart payload returns the deity name and the krura_saumya field for each planet in D60, plus the Lagna's D60 deity. This is the field rectification work depends on - a one-minute birth-time shift can move a planet to a different D60 division.

Mean vs True nodes - which does the chart use?

Either - your choice. Set node_type=mean for the smoothed Parashara default, or node_type=true for the osculating node used in some modern Western and a few Vedic schools. The value comes back in the response payload so the chart's audit trail records which convention produced it. No silent defaults. If you do not set node_type, the chart uses mean.

What is a Vedic birth chart (Kundli) and how is it different from Western?

A Kundli uses the sidereal zodiac (actual star positions). Western uses tropical (tied to seasons). There is currently a ~24 degree gap, called ayanamsa, between the two. So your Vedic sun sign is usually one sign behind your Western sun sign. Kundlis also include Nakshatras (27 lunar mansions), Vimshottari Dasha (planetary periods), and use Whole Sign houses by default. Our API generates Kundlis in <300ms with Swiss Ephemeris (NASA JPL data) precision and supports 12 ayanamsa systems.

How do I generate a Kundli using your API?

POST to /api/v3/vedic/kundli with birth data (date, time, location) and your settings: ayanamsa (default lahiri), house_system (default whole_sign), node_type (default mean), include_dasha if you want the 120-year timeline. The response includes sidereal positions, Nakshatra with pada, Ascendant, house placements, the six Shadbala components per planet, Bhava Bala per house, optional D60 with deity, and Vimshottari Dasha starting point. <300ms. SDKs for JavaScript, Python, PHP with copy-paste examples.

Do you calculate birth Nakshatra automatically?

Yes. Every Kundli includes the birth Nakshatra: Nakshatra name (Rohini, Ashwini, and so on), pada (1 to 4), lord (ruling planet), deity, symbol, and characteristics. Birth Nakshatra determines the Vimshottari Dasha starting point. Swiss Ephemeris precision - accurate to 1 arc-minute. The full 108-division mapping (27 nakshatras x 4 padas) is exposed.

Can I get both Western and Vedic birth charts from your API?

Yes. Set include_western: true and include_vedic: true in your request. The response returns a Western chart with tropical zodiac and Placidus houses, plus a Vedic chart with sidereal zodiac (12 ayanamsas available, Lahiri default), Whole Sign houses, Nakshatras, and the Shadbala payload. <300ms for both. Most APIs make you choose - we return both from one call.

How accurate are your Kundli calculations?

Swiss Ephemeris (NASA JPL data) with 0.001 degree precision. Same engine as Parashara's Light and Jagannatha Hora. Lahiri ayanamsa accounts for exact birth date (the value shifts ~50 arc-seconds per year). Nakshatra positions accurate to 1 arc-minute. For comparison: manual table-based calculation has 5-10 arc-minute error.

How much does Vedic birth chart API cost?

$11/month for 1,000 Kundli generations with Shadbala fields, Nakshatras, Vimshottari Dasha starting point, and Mean/True node toggle. Free tier: 50 Kundlis/month forever. Professional ($37/mo): 55,000 requests with all 16 divisional charts (including D60 with deity), Kundli matching, Bhava Bala access, yoga detection. Prokerala charges $29-499/mo for less depth. Desktop software is $500-2000 one-time and does not scale.

Is there a free tier for testing?

Yes. 50 Kundli generations per month with the full classical payload: Swiss Ephemeris precision, Lahiri default (all 12 ayanamsas selectable), Shadbala component fields, Nakshatra with pada, Whole Sign houses, Mean/True node toggle, Vimshottari Dasha starting point, AI interpretations in 13 languages. Sign up and get an API key instantly. Upgrade to Starter or Professional when you scale.

What's included in the Professional tier?

Professional ($37/mo): 55,000 Kundli requests/month, all 16 divisional charts (D1-D60, including D60 with deity and Krura/Saumya), Kundli matching with 36 Gunas, Mangal Dosha detection, 500+ yoga detection, full Shadbala breakdown, Bhava Bala on every house, Vimsopaka three schemes, Mean/True node toggle, 13 languages, priority email support, webhook notifications.

How long does integration take?

Most developers ship in 2-4 hours. SDKs for JavaScript, Python, PHP plus REST docs with copy-paste examples. Bearer token auth. JSON response. First successful Kundli call inside 15 minutes if you know REST. Versus 6+ months minimum to learn Vedic astronomy and code ayanamsa, Nakshatra divisions, Shadbala, and house systems from scratch.

Do you support Indian regional languages?

Yes. 13 languages: 8 Indian (Hindi, Tamil, Telugu, Kannada, Malayalam, Bengali, Gujarati, Marathi) and 5 European (English, Russian, Spanish, German, French). Set language: hi for Hindi or language: ta for Tamil and the interpretations - Nakshatra descriptions, Dasha predictions, planetary characteristics, yogas - come back in that language. Most competitors stop at English plus Hindi.

Can I white-label the Kundli interpretations?

Yes. Enterprise tier ($399+/mo) includes white-label interpretations - customize Nakshatra descriptions, Dasha predictions, planetary characteristics, yoga explanations, and remedies to match your brand voice. Professional ($37/mo) gets AI-generated unique interpretations - each Kundli has personalized text based on the actual planetary positions. Free and Starter use standard interpretations.

How is this different from Prokerala Kundli API?

Prokerala returns a basic Kundli, no six-fold Shadbala in the chart payload, no D60 deity, no Mean/True node toggle, hardcoded ayanamsa choice. Our chart endpoint ships the classical fields directly: Shadbala components per planet, D60 deity + Krura/Saumya, Bhava Bala per house, node_type echoed in response. <300ms vs Prokerala's 2-3 seconds. $11-399/mo vs $29-499/mo. We also return both Western and Vedic in one call. If you need a basic Kundli for India only, Prokerala works. For classical depth or both systems, choose us.

How does this compare to VedicRishi?

VedicRishi has more depth than Prokerala but returns Shadbala as a single total without component breakdowns and does not expose D60 deity or Krura/Saumya nature. Our chart payload returns each of the six Shadbala components with sub-parts, the D60 deity name, and the krura_saumya field per planet in D60. We also expose Mean / True node selection with audit trail in the response. Pricing is comparable; the depth is not.

Why not use desktop software like Parashara's Light or Jagannatha Hora?

Desktop software costs $500-2000 one-time and only runs on one computer. Building an API wrapper around it takes 3+ months. Our API is cloud-based and scales to millions of requests for $11-399/month. Same Swiss Ephemeris engine, identical accuracy. Desktop software is great for one astrologer; terrible for an app serving thousands of users.

Can I use this for marriage matching apps?

Yes. Generate Kundlis for both partners, then send them to the Kundli matching endpoint for the full Ashtakoot: 8 Kutas (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi) totaling 36 Gunas. Also detects Mangal Dosha from Lagna, Moon, or Venus, plus Nadi Dosha. Compatibility score with per-Kuta explanations. <800ms for two full Kundlis matched. Professional tier ($37/mo) gives unlimited matching. Used by matrimony platforms processing 1000+ matches daily. Bhava Bala on the 7th house adds another grade on marriage prospects.

What house system do you use for Vedic charts?

Whole Sign by default (each zodiac sign equals one house - the traditional Vedic standard used for 2,000+ years). Equal and Porphyry are also available for Vedic. For Western charts, all 23 systems including Placidus, Koch, and Campanus - and the test suite covers the obscure ones too. Set house_system: whole_sign for Vedic or house_system: placidus for Western.

Do you include Vimshottari Dasha in the Kundli?

Yes. The chart response includes the Vimshottari Dasha starting point - which Mahadasha you were born into, derived from Moon's nakshatra and proportionally adjusted for how far the Moon has traveled through that nakshatra. Set include_dasha: true and the full 120-year timeline is returned: 10 Mahadashas, 9 Antardashas each, 9 Pratyantardashas each. Without Dasha context, Vedic predictions are generic.

Can I use the chart payload for birth time rectification?

Yes - this is the use case the recent changes were built for. D60 deity name, D60 Krura/Saumya nature, and the Mean/True node toggle were added at the request of closed-beta partners doing rectification work. Generate the chart at a candidate time, read the Lagna's D60 deity, check whether key planets sit on Krura or Saumya divisions, and confirm the time against the client's life events. The node_type echo in the response makes the audit trail explicit.

Birth Chart Vedic API

Generate Kundlis with D60 Deity and Classical Shadbala

Kundli payload includes classical Shadbala fields, D60 deity + Krura/Saumya nature, Mean/True node toggle, Bhava Bala access, and Vimshottari Dasha starting point.

Swiss Ephemeris precision, 12 ayanamsas, <300ms response.

View Documentation

D60 deity

+ Krura/Saumya

Shadbala

6 components

Mean/True

Node toggle

<300ms

Response time

2.3M+ Kundlis generated monthly

Swiss Ephemeris (NASA JPL data)

Both Western + Vedic in one API

Planetary positions only - no Shadbala component fields in the chart payload
D60 returned as a sign, with no deity name and no Krura/Saumya nature
Node calculation is hardcoded - no Mean vs True choice, no audit trail
House strength (Bhava Bala) is not accessible from the chart endpoint
Vimshottari Dasha starting point depends on birth Nakshatra and is often skipped
Lahiri only, instead of the 12 ayanamsa systems serious astrologers use

From basic placements to a classical Kundli payload

Classical Shadbala fields per planet (Sthana, Dig, Kala, Cheshta, Naisargika, Drik)
D60 Shashtiamsa returns deity name + Krura/Saumya nature for every planet
Mean / True node toggle (node_type=mean or true) echoed in the response for audit
Bhava Bala accessible from the chart endpoint, not just the planetary strength endpoint
Vimshottari Dasha starting point from Moon nakshatra, proportionally adjusted
12 ayanamsa systems and Swiss Ephemeris with 0.001 degree precision in <300ms

Performance Metrics

Enterprise-grade reliability

Vedic Birth Chart (Kundli) API - Shadbala, D60 Deity, Mean/True Nodes

Classical Kundli payload: Shadbala fields, D60 deity + Krura/Saumya, node toggle, Bhava Bala access

A Vedic birth chart (Kundli or Janam Kundali) uses the sidereal zodiac - actual star positions - instead of the tropical zodiac Western charts use. There is roughly 24 degree of drift between the two systems due to precession, and ayanamsa is the correction factor that bridges them. Our Kundli API generates Vedic birth charts in <300ms on Swiss Ephemeris with 0.001 degree precision. The new payload ships the classical fields working astrologers asked for: six-fold Shadbala per planet (Sthana, Dig, Kala, Cheshta, Naisargika, Drik), D60 Shashtiamsa with deity name and Krura/Saumya nature, Mean / True node toggle echoed in the response for audit, and Bhava Bala accessible from the chart endpoint without a second call. Twelve ayanamsa systems are supported (Lahiri default), birth Nakshatra with pada is included, Vimshottari Dasha starting point is computed from Moon's nakshatra position, and Whole Sign houses are the default. Over 2,800 developers and astrologers use the API to generate 2.3M+ Kundlis monthly. Still the only API that returns both Western and Vedic from one call.

What is in the classical Kundli payload?

The chart endpoint now returns more than placements.

For every planet you get: sidereal longitude with Swiss Ephemeris precision, sign and house, Nakshatra and pada, dignity, retrograde flag - and the six classical Shadbala components: Sthana Bala, Dig Bala, Kala Bala, Cheshta Bala, Naisargika Bala, Drik Bala.

Each comes with its sub-parts plus Ishta and Kashta phala.

So a single Kundli call gives you the same strength data a working Parashara astrologer reaches for, instead of forcing a second endpoint.

The Lagna (Ascendant) is returned with the same fields.

Vimshottari Dasha starting point is included - the Mahadasha you were born into, derived from Moon's nakshatra.

Set include_dasha=true to get the full 120-year timeline with three levels (Maha, Antar, Pratyantar).

Six Shadbala components per planet - in the chart response

1 min read

D60 deity and Krura/Saumya in the chart response

The Shashtiamsa (D60) divides each sign into 60 parts of 0 degree 30 minute each.

Each of those 60 has a Parashara deity name and a classical nature: Krura (harsh) or Saumya (gentle).

The chart payload now includes the deity name (Ghora, Rakshasa, Deva, Kubera, Yaksha, Kinnara and so on) plus krura_saumya for every planet placed in D60.

This is the one chart where a one-minute birth-time shift can move a planet to a different division, which is why it is the chart rectification work depends on.

The Lagna's D60 deity is one of the strongest classical confirmations of a rectified time.

Prokerala and VedicRishi return the D60 sign and that is it; the deity and nature fields are simply not there.

D60 deity + nature in the chart - not just the sign

1 min read

Mean vs True node toggle in chart data

Rahu and Ketu can be computed two ways.

Mean nodes use a smoothed, slowly-moving lunar node - the traditional Parashara choice.

True nodes use the osculating node, which oscillates around the mean and is preferred by some modern Western and a few Vedic schools.

Most APIs hardcode one or the other and never tell you.

Ours exposes a node_type field: set it to mean or true.

The chosen value comes back in the response payload, so a chart's audit log shows which convention produced it.

Two practitioners can now compare results without arguing about silent defaults.

Default is mean if you do not set the field.

node_type set per call, echoed in response, no silent defaults

1 min read

Classical Shadbala fields in the chart payload

Each planet in the chart now ships with its full Shadbala breakdown.

Sthana Bala is positional - dignity, exaltation, varga placements (Saptavargaja Bala, Ojhayugma Bala, Kendradi Bala, Drekkana Bala).

Dig Bala is directional - Sun and Mars are strongest in the 10th, Jupiter and Mercury in the 1st, Moon and Venus in the 4th, Saturn in the 7th.

Kala Bala is temporal and has eight sub-components including Nathonatha (day-night), Paksha (waxing-waning Moon), Hora (planetary hour), Ayana, Yuddha (planetary war).

Cheshta Bala measures motion - retrograde planets get high Cheshta Bala.

Naisargika Bala is the fixed natural order Sun > Moon > Venus > Jupiter > Mercury > Mars > Saturn.

Drik Bala scores benefic-minus-malefic aspect.

Sum the six and you have Shadbala Pinda.

The response also includes Ishta phala (favorable result) and Kashta phala (harsh result) derived from Shadbala.

Most APIs return a single total.

Ours returns the breakdown so you can show users why a planet is strong or weak component by component.

Six components with sub-parts plus Ishta/Kashta phala

1 min read

Bhava Bala accessible from the chart endpoint

Bhava Bala scores a house, not a planet, and the two calculations rank charts differently.

A house can be strong even when its lord is weak elsewhere.

The chart endpoint now exposes Bhava Bala directly - no second call.

For each house you get Bhavadhipati Bala (strength of the house lord), Bhava Digbala (directional strength of the bhava), and Bhava Drik Bala (aspect strength on the bhava).

Useful when the question is which house can deliver results: career, marriage, health, wealth.

Example: in a chart with weak Saturn, the 10th can still rank high in Bhava Bala because of strong aspects on the 10th and a well-placed 10th lord.

The chart endpoint returns this without recomputing the full Kundli.

House strength alongside planetary strength - one call

1 min read

Why Lahiri ayanamsa is the Kundli default

Ayanamsa is the offset between tropical and sidereal zodiacs.

Twelve ayanamsa systems are supported: Lahiri, Krishnamurti (KP), Raman, Yukteshwar, True Citra, JN Bhasin, Ushashashi, True Revati, True Pushya, SS Citra, Suryasiddhanta, Fagan-Bradley.

Lahiri is the Indian government standard and the working default for ~90% of Vedic astrologers, so the API uses it unless you ask otherwise.

Lahiri currently puts the gap at ~24 degree, with about 50 arc-seconds added per year due to precession.

KP practitioners should set ayanamsa=krishnamurti.

Western chart needs no ayanamsa at all.

For developers serving both audiences, the same birth data can produce a tropical Western chart and a sidereal Vedic Kundli in one response.

12 ayanamsa systems, Lahiri default, both Western and Vedic in one call

1 min read

Use Cases

Marriage & Dating Apps

Generate Kundlis for new user profiles, auto-match with Gun Milan, use Bhava Bala on the 7th to grade marriage prospects

Birth Time Rectification

D60 deity + Krura/Saumya nature plus Mean/True node toggle - the exact fields rectification work needs

Professional Astrologer Tools

Six-fold Shadbala in the chart payload, all 16 divisional charts, Bhava Bala accessible from the chart endpoint

Daily Horoscope Apps

Personalized predictions from birth Nakshatra and the current Vimshottari Dasha period

Learning Platforms

Compare Western and Vedic side-by-side, teach Parashara classical math with documented rule sources

AI Astrology Apps

Feed the classical Kundli payload to LLMs - Shadbala, Bhava Bala, D60 deity give the model real Parashara structure

Technical Specifications

API Response Time	<300ms average for the classical Kundli payload
Calculation Engine	Swiss Ephemeris (NASA JPL data) with 0.001 degree precision
Default Ayanamsa	Lahiri (~24 degree currently)
Supported Ayanamsas	12 systems: Lahiri, Krishnamurti (KP), Raman, Yukteshwar, True Citra, JN Bhasin, Ushashashi, True Revati, True Pushya, SS Citra, Suryasiddhanta, Fagan-Bradley
Shadbala fields in chart	Sthana, Dig, Kala, Cheshta, Naisargika, Drik per planet, plus Ishta/Kashta phala
D60 detail	deity name + krura_saumya nature per planet
Bhava Bala	Bhavadhipati, Bhava Digbala, Bhava Drik Bala per house - accessible from chart endpoint
Node type	node_type enum: mean (default) or true, echoed in response
Zodiac System	Sidereal (Vedic) + Tropical (Western) in one call
House System	Whole Sign (default), Equal, Porphyry + 23 Western systems
Nakshatras	All 27 with 4 padas each (108 divisions)
Vimshottari Dasha	Starting Mahadasha from Moon nakshatra; full 3-level timeline on request
Planetary Positions	Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Rahu, Ketu
Divisional Charts	Optional: D1, D9, D10, D12, D60 (all 16 Parashara vargas available)
Languages Supported	13 languages (8 Indian + 5 European)
Response Format	Clean JSON with structured planetary data
Authentication	Bearer token (API key)
Integration Time	2-4 hours with SDKs (JavaScript, Python, PHP, REST)
Free Tier Limits	50 Kundlis/month forever with full features

Related Vedic Astrology APIs

Vedic Astrology API

Full classical suite: Shadbala, Bhava Bala, Vimsopaka, all 16 Parashara vargas

Vimshottari Dasha API

Planetary periods - 10 Maha + 9 Antar + 9 Pratyantar - for timing predictions

Nakshatra Calculator API

27 lunar mansions with padas, lords, deities, characteristics

Navamsa Calculator API

D9 chart for marriage predictions and spouse characteristics

Divisional Charts API

Full D1-D60 Parashara varga set with documented rule sources

Karmic Astrology API

Rahu, Ketu, and D60 deity work for past-life and karmic analysis

Western Birth Chart API

Compare: tropical (Western) birth charts with Placidus houses

API Documentation

Complete technical reference with authentication and code examples

References & Standards

Swiss Ephemeris (DE431-based) — astronomical calculations source
NASA JPL Planetary Ephemerides — underlying ephemeris dataset
International Astronomical Union (IAU) — body designation and nomenclature standards
IANA Time Zone Database — timezone & DST resolution

Classical Kundli Payload

Classical Shadbala fields per planet

The chart payload includes the six classical strength components: Sthana, Dig, Kala, Cheshta, Naisargika, Drik. Not a single total - the breakdown.

Per Brihat Parashara Hora Shastra

D60 deity + Krura/Saumya nature

Shashtiamsa returns deity name (Ghora, Rakshasa, Deva, Kubera, Yaksha, Kinnara, etc.) and the classical nature for every planet. Critical for rectification.

60 divisions of 0 degree 30 minute each

Mean / True node toggle

Pick node_type=mean (Parashara default) or node_type=true (osculating). The chosen value is returned in the response payload for audit.

Audit trail in every chart

Bhava Bala from chart endpoint

House strength (Bhavadhipati, Bhava Digbala, Bhava Drik Bala) accessible directly from the Kundli endpoint - no second call.

Three classical components per house

12 Ayanamsa Systems

Lahiri (default, ~24 degree correction), Krishnamurti (KP), Raman, Yukteshwar, True Citra, JN Bhasin, Ushashashi, True Revati, True Pushya, SS Citra, Suryasiddhanta, Fagan-Bradley.

Widest ayanamsa coverage of any API

27 Nakshatras with Padas

Birth Nakshatra with 4 pada subdivisions, lord, deity, symbol, and characteristics. Essential for Dasha calculation.

108 total divisions

Whole Sign Houses

Vedic standard for 2,000+ years - each zodiac sign is one house. Equal and Porphyry also supported.

Plus 23 Western house systems

Vimshottari Dasha starting point

The Mahadasha you were born into is determined by Moon's Nakshatra and proportionally adjusted for travel within that nakshatra.

120-year timeline available on request

Sidereal Planetary Positions

All 9 planets sidereal: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Rahu, Ketu - Swiss Ephemeris precision.

0.001 degree accuracy

Both Western + Vedic

Tropical (Western) and sidereal (Vedic) positions in one API call. Side-by-side comparison built in.

Only API that returns both

Marriage Matching Ready

Kundlis include Nakshatra, Rasi, and Navamsa - the data the matching endpoint needs for the 36 Gunas.

Feed straight into Kundli matching

13 Languages

8 Indian (Hindi, Tamil, Telugu, Kannada, Malayalam, Bengali, Gujarati, Marathi) and 5 European (English, Russian, Spanish, German, French).

Regional and global markets covered

Vedic Birth Chart API Comparison

How we compare to Prokerala, VedicRishi, and desktop software

Feature	Astrology API	Prokerala	VedicRishi	Desktop Software
Classical Shadbala in chart payloadComponent breakdowns, not totals	Six components with breakdowns	Total only or missing	Total only	Yes (Parashara's Light)
D60 deity + Krura/SaumyaCritical for rectification	Returned	Not exposed	Not exposed	Yes
Mean / True node toggleAudit trail per chart	Yes - echoed in response	Hardcoded	Hardcoded	Configurable
Bhava Bala from chart endpointNo second call needed	Yes	No	Separate endpoint only	Yes
Response Time300x faster than desktop	<300ms	2-3 seconds	1-2 seconds	2-5 seconds
Ayanamsa OptionsWidest ayanamsa coverage of any API	12 systems	Lahiri only	Lahiri, Raman	Lahiri, Raman
Both Western + VedicOnly API with both systems	Yes (one call)	No (Vedic only)	No (Vedic only)	Separate modes
Nakshatra Calculation	Auto with Pada	Basic	With Pada	Yes
Vimshottari Dasha starting point	In chart response	Separate call	Separate call	Yes
Divisional Charts	Optional D1-D60	D1, D9, D10	D1-D30	All available
AccuracyNASA JPL precision	Swiss Ephemeris 0.001 degree	Good	Swiss Ephemeris	Swiss Ephemeris
ScalabilityCloud-based unlimited scale	Millions/day	Limited	Limited	One user
Cost4-5x cheaper than competitors	$11-399/month	$29-499/month	$49-299/month	$500-2000 one-time
Integration Time	2-4 hours	1-2 days	1-2 days	API wrapper needed

Best Choice

Classical Shadbala in chart payload

Component breakdowns, not totals

Astrology API

Six components with breakdowns

Prokerala

Total only or missing

VedicRishi

Total only

Desktop Software

Yes (Parashara's Light)

Best Choice

D60 deity + Krura/Saumya

Critical for rectification

Astrology API

Returned

Prokerala

Not exposed

VedicRishi

Not exposed

Desktop Software

Yes

Best Choice

Mean / True node toggle

Audit trail per chart

Astrology API

Yes - echoed in response

Prokerala

Hardcoded

VedicRishi

Hardcoded

Desktop Software

Configurable

Best Choice

Bhava Bala from chart endpoint

No second call needed

Astrology API

Yes

Prokerala

VedicRishi

Separate endpoint only

Desktop Software

Yes

Best Choice

Response Time

300x faster than desktop

Astrology API

<300ms

Prokerala

2-3 seconds

VedicRishi

1-2 seconds

Desktop Software

2-5 seconds

Best Choice

Ayanamsa Options

Widest ayanamsa coverage of any API

Astrology API

12 systems

Prokerala

Lahiri only

VedicRishi

Lahiri, Raman

Desktop Software

Lahiri, Raman

Best Choice

Both Western + Vedic

Only API with both systems

Astrology API

Yes (one call)

Prokerala

No (Vedic only)

VedicRishi

No (Vedic only)

Desktop Software

Separate modes

Nakshatra Calculation

Astrology API

Auto with Pada

Prokerala

Basic

VedicRishi

With Pada

Desktop Software

Yes

Vimshottari Dasha starting point

Astrology API

In chart response

Prokerala

Separate call

VedicRishi

Separate call

Desktop Software

Yes

Divisional Charts

Astrology API

Optional D1-D60

Prokerala

D1, D9, D10

VedicRishi

D1-D30

Desktop Software

All available

Best Choice

Accuracy

NASA JPL precision

Astrology API

Swiss Ephemeris 0.001 degree

Prokerala

Good

VedicRishi

Swiss Ephemeris

Desktop Software

Swiss Ephemeris

Best Choice

Scalability

Cloud-based unlimited scale

Astrology API

Millions/day

Prokerala

Limited

VedicRishi

Limited

Desktop Software

One user

Best Choice

Cost

4-5x cheaper than competitors

Astrology API

$11-399/month

Prokerala

$29-499/month

VedicRishi

$49-299/month

Desktop Software

$500-2000 one-time

Integration Time

Astrology API

2-4 hours

Prokerala

1-2 days

VedicRishi

1-2 days

Desktop Software

API wrapper needed

Frequently Asked Questions

Vedic Birth Chart (Kundli) API - Shadbala, D60 deity, Mean/True nodes, Bhava Bala

Simple, Transparent Pricing

Start free, scale as you grow. No hidden fees, no surprises.

Always Free

Start Free

Perfect for learning, testing, and small personal projects

50 API calls/month

Basic natal charts

5 house systems

Community support

Pro

$11/month

For small apps and personal projects

All basic endpoints
12 house systems
Email support

Best Value

Pro Plus

$21/month

For growing apps and medium traffic

All enhanced endpoints
18 house systems
AI interpretations
Priority email support

Ultra

$37/month

For professional astrology applications

Credit math ↓

All premium endpoints
23 house systems
Advanced AI interpretations
Priority support

High Volume Plans

For enterprise-scale applications

Business

$99/month

For high-volume applications

Credit math ↓

ALL endpoints
White-label ready
Custom AI fine-tuning
Phone support

UNLIMITED

Enterprise

$399+per month

Unlimited requests with dedicated infrastructure

Dedicated server infrastructure
Sub-300ms guaranteed
24/7 dedicated support
99.99% uptime SLA

All plans include comprehensive documentation and SDKs

Questions? Talk to our team

50 free requests/month

Start Generating Kundlis Today

Join 2,800+ developers and astrologers using our API for Vedic birth chart generation with Nakshatras and Vimshottari Dasha

<300ms

Kundli Generation

Nakshatras

Languages

Get Free API Key View Documentation

Start Free

Full Vedic Features

Cancel Anytime

Free tier includes 50 Kundlis/month with Nakshatras and Dasha

Generate Kundlis with D60 Deity and Classical Shadbala

Most Kundli APIs return placements without classical depth

Kundli payload with the classical fields actually used by astrologers

Performance Metrics

Vedic Birth Chart (Kundli) API - Shadbala, D60 Deity, Mean/True Nodes

What is in the classical Kundli payload?

D60 deity and Krura/Saumya in the chart response

Mean vs True node toggle in chart data

Classical Shadbala fields in the chart payload

Bhava Bala accessible from the chart endpoint

Why Lahiri ayanamsa is the Kundli default

Use Cases

Marriage & Dating Apps

Birth Time Rectification

Professional Astrologer Tools

Daily Horoscope Apps

Learning Platforms

AI Astrology Apps

Technical Specifications

Related Vedic Astrology APIs

Vedic Astrology API

Vimshottari Dasha API

Nakshatra Calculator API

Navamsa Calculator API

Divisional Charts API

Karmic Astrology API

Western Birth Chart API

API Documentation

References & Standards

Classical Kundli Payload

Classical Shadbala fields per planet

D60 deity + Krura/Saumya nature

Mean / True node toggle

Bhava Bala from chart endpoint

12 Ayanamsa Systems

27 Nakshatras with Padas

Whole Sign Houses

Vimshottari Dasha starting point

Sidereal Planetary Positions

Both Western + Vedic

Marriage Matching Ready

13 Languages

Vedic Birth Chart API Comparison

Classical Shadbala in chart payload

D60 deity + Krura/Saumya

Mean / True node toggle

Bhava Bala from chart endpoint

Response Time

Ayanamsa Options

Both Western + Vedic

Nakshatra Calculation

Vimshottari Dasha starting point

Divisional Charts

Accuracy

Scalability

Cost

Integration Time

Frequently Asked Questions

Does the chart payload include classical Shadbala fields?

Does the API return D60 deity and Krura/Saumya nature?

Mean vs True nodes - which does the chart use?

Is Bhava Bala accessible from the chart endpoint?

What is a Vedic birth chart (Kundli) and how is it different from Western?

How do I generate a Kundli using your API?

Which ayanamsa should I use for Kundli generation?

Do you calculate birth Nakshatra automatically?

Can I get both Western and Vedic birth charts from your API?

How accurate are your Kundli calculations?

How much does Vedic birth chart API cost?

Is there a free tier for testing?

What's included in the Professional tier?

How long does integration take?

Do you support Indian regional languages?

Can I white-label the Kundli interpretations?

How is this different from Prokerala Kundli API?

How does this compare to VedicRishi?

Why not use desktop software like Parashara's Light or Jagannatha Hora?

Can I use this for marriage matching apps?

What house system do you use for Vedic charts?

Do you include Vimshottari Dasha in the Kundli?