The Navamsa (D9) chart: marriage and dharma via API

The Navamsa, or D9 chart, is the ninth divisional chart of Vedic astrology and the one astrologers read most closely for marriage, the spouse, and a person's dharma. You can compute it through the Vedika API in two ways: ask a natural-language marriage question at POST /api/v1/astrology/query and the engine derives the D9 internally, or call the V2 computation endpoints to get the raw Navamsa positions for your own renderer. Both paths return code-computed positions from the XALEN ephemeris, and the AI path layers a source-cited reading on top.

What the Navamsa (D9) chart actually is

A divisional chart (varga) subdivides each zodiac sign and re-maps the parts onto a fresh chart. For the Navamsa, each 30° sign is split into nine equal parts of 3°20' each. A planet's degree within its sign determines which of the nine parts it falls in, and that part is assigned a sign by a fixed rule that depends on whether the originating sign is movable, fixed, or dual. The result is a second twelve-house chart built entirely from the same birth instant.

Because the Navamsa magnifies the fractional position of each planet, two people born minutes apart can share a near-identical birth chart yet diverge sharply in the D9. That sensitivity is exactly why it is treated as a strength test: a planet that is dignified in the birth chart but falls into a debilitated Navamsa sign is considered to promise less than it appears to.

Why marriage and dharma map to the ninth harmonic

In the classical framework, the ninth house and the number nine are tied to dharma, fortune, and the higher purpose a life is oriented toward. Brihat Parashara Hora Shastra directs the reader to the Navamsa for the strength of planets and for matters of the spouse, and Phaladeepika reinforces the D9 as the chart of marriage. Reading the seventh house and its lord in the D9, the placement of Venus (the natural significator of relationships), and the Navamsa lagna together gives a layered view that a single birth chart cannot.

Key facts

• The Navamsa divides each 30° sign into nine parts of 3°20', producing the D9 chart from the birth moment.
• It is the primary chart for marriage, the spouse, and dharma in Jyotish, and a strength test for every planet.
• A planet in the same sign in both D1 and D9 is vargottama — a marker of stability for that planet.
• The Darakaraka (Jaimini's spouse significator) is the planet at the lowest degree; its Navamsa placement informs the marriage reading.
• Vedika computes Vedic, Western, and KP in one API, plus Jaimini, so D9 and Chara Karakas come from the same call shape.
• Positions are computed by the XALEN Ephemeris, an open-source engine validated against JPL DE440 reference data to within 0.1° across a large test set.

Computing the D9 through the API

The fastest way to see a Navamsa-aware answer is the natural-language query endpoint. Send the question plus structured birth details and the engine selects the relevant charts, computes the D9, and returns a reading. Authenticate with your live key in the x-api-key header.

curl -X POST https://api.vedika.io/api/v1/astrology/query \
  -H "x-api-key: vk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "What does my Navamsa chart say about marriage and my spouse?",
    "birthDetails": {
      "datetime": "1992-03-14T09:25:00",
      "latitude": 19.0760,
      "longitude": 72.8777,
      "timezone": "Asia/Kolkata"
    }
  }'

If you want the raw divisional positions to drive your own chart UI, use the V2 computation surface. V2 takes flat datetime, latitude, longitude, and timezone fields rather than a nested object, which keeps it convenient to call from form inputs.

import requests

BASE = "https://api.vedika.io"
HEADERS = {"x-api-key": "vk_live_your_key_here"}

# Compute Vedic divisional charts including the Navamsa (D9)
resp = requests.post(
    f"{BASE}/v2/astrology/divisional-charts",
    headers=HEADERS,
    json={
        "datetime": "1992-03-14T09:25:00",
        "latitude": 19.0760,
        "longitude": 72.8777,
        "timezone": "Asia/Kolkata",
        "charts": ["D1", "D9"],
    },
)
data = resp.json()

# Detect vargottama: same sign in D1 and D9
d1 = {p["name"]: p["sign"] for p in data["D1"]["planets"]}
d9 = {p["name"]: p["sign"] for p in data["D9"]["planets"]}
vargottama = [name for name in d1 if d1[name] == d9.get(name)]
print("Vargottama planets:", vargottama)

The exact key names and the full divisional list are in the API reference. You can run both of these calls against the free sandbox with no key while you wire up the request shape.

Streaming the reading

For chat-style interfaces, the same question can be sent to /api/v1/astrology/query/stream, which returns Server-Sent Events so the interpretation renders token by token while the chart computation runs once up front. The streaming and non-streaming endpoints accept the same body, so you can switch on the client side without changing your request builder.

Reading the Navamsa: what to look at

A practical D9 marriage read combines several computed signals. The API returns each of these so your application, or an LLM agent built on top of it, can reason over structured fields instead of guessing.

Vargottama and dignity in one comparison

The Python snippet above already shows the cleanest vargottama check: compare the D1 and D9 sign of each body and flag the matches. Layer dignity on top — exaltation, own sign, or debilitation in the Navamsa — and you get a fast read on which promises in the birth chart are reinforced and which are hollow. This is the kind of derived field that turns a divisional chart from a picture into something a program can act on.

The Darakaraka and Jaimini layer

Because Vedika computes Jaimini alongside the parashari Vedic system, the Chara Karakas come from the same birth call. The Darakaraka — the planet sitting at the lowest degree of any sign — is the Jaimini significator of the spouse. Reading the sign and house it falls in within the Navamsa, per the Jaimini Sutras, adds a second, independent description of the marriage partner that you can present beside the parashari reading.

Grounding every claim in classical sources

Computed positions are deterministic, but interpretation is where most astrology tools quietly drift into invented authority. Vedika separates the two. The ephemeris produces the numbers; the interpretive layer attributes its claims to classical texts that practitioners are actually trained from — Brihat Parashara Hora Shastra, Phaladeepika, Saravali, the Jaimini Sutras, and the Western and KP equivalents for those systems. The engine does not fabricate verse numbers or paraphrase web summaries as if they were scripture.

For a B2B integration this matters beyond aesthetics. If your product surfaces a marriage prediction to an end user, the difference between “the D9 shows a delayed marriage because Saturn aspects the seventh” with a real source and the same sentence with no provenance is the difference between a defensible feature and a liability. The citation discipline is built into the response, not bolted on after.

One API, three systems, and an MCP path

The Navamsa is a Vedic construct, but the same birth call also returns Western (tropical) and KP results when you ask for them — three astrology systems behind one set of endpoints, alongside Jaimini, Tajaka, Lal Kitab, and numerology. There are 700+ operations across 25 domains, so the D9 work described here is one slice of a broad surface. Responses are available in 30 languages, including 14 Indic languages, if you are serving an Indian or diaspora audience directly.

If you are building an AI assistant rather than a classic backend, the public MCP server (npx @vedika-io/mcp-server) exposes the same computation as tools an MCP-compatible client can call, so a function-calling model can request a Navamsa reading the same way it would call any other tool. The chart math runs server-side; your model only orchestrates.

Where it fits versus other providers

Several established providers expose divisional charts. Prokerala (around $19/mo) and AstrologyAPI.com (around $29/mo) both have mature catalogs and solid documentation, and RoxyAPI (around $39/mo) covers a wide endpoint range. If your need is purely a static D9 image or a position table, any of them will serve.

Vedika's differentiators are specific: an open-source, independently verifiable ephemeris (the XALEN Ephemeris, Apache-2.0, with crates.io, PyPI, and WASM packages and roughly 2,200 tests); three systems plus Jaimini behind one call so vargottama and Darakaraka come from the same request; source-cited interpretation rather than unattributed text; and the natural-language and MCP paths for teams putting an LLM in front of the chart. Pricing starts at $12/mo (Starter), with Professional at $60, Business at $120, and Enterprise at $240; see pricing for the per-query rates and the fast and voice add-ons.

Next steps

Try the natural-language marriage question against the sandbox first to see the shape of a Navamsa reading, then switch to the V2 divisional endpoint when you need raw positions for your own renderer. The vargottama detection snippet above is a good first derived field to ship. For the divisional system more broadly, read the divisional charts reference.

FAQ

What is the Navamsa (D9) chart and why does it matter for marriage?

It is the ninth harmonic divisional chart, dividing each sign into nine 3°20' parts. In Jyotish it is the primary chart for marriage, the spouse, and dharma, and it tests the underlying strength of every planet in the birth chart.

How do I compute a Navamsa chart through the Vedika API?

Call the V2 computation endpoint with flat datetime, latitude, longitude, and timezone and request the divisional charts, or ask a marriage question at POST /api/v1/astrology/query and the engine computes the D9 internally.

What is vargottama and does the API flag it?

A planet is vargottama when it sits in the same sign in D1 and D9, a marker of stability. The output includes each planet's D1 and D9 sign so you can detect it directly, and the reading surfaces it when present.

Can the API read Darakaraka and Jaimini significators for the spouse?

Yes. Jaimini runs alongside Vedic, so the Chara Karakas including the Darakaraka are computed, and its Navamsa placement is part of the marriage reading.