Chara Dasha (Jaimini) timing via API

Chara Dasha is a sign-based predictive timing system from the Jaimini school of Vedic astrology, and you can compute it directly through the Vedika API by sending birth details to the astrology endpoints. Unlike the planet-based Vimshottari Dasha that most tools default to, Chara Dasha assigns periods to zodiac signs, with the length of each period derived from the position of that sign's lord. The API returns the ordered sign periods together with the derived Atmakaraka, Amatyakaraka, and Karakamsa so you can build Jaimini-style readings without hand-calculating the chara karakas yourself.

What Chara Dasha is, and why it needs its own endpoint

Most dasha implementations stop at Vimshottari. That covers the common case, but the Jaimini tradition uses a different timing model that experienced astrologers reach for when Vimshottari alone does not explain the timeline of events. The two systems answer the same question — "when?" — from different mathematical bases, and a serious astrology product usually exposes both.

The core distinction is structural:

Because the period length is computed (not looked up from a fixed table), and because the cycle can run forward or backward depending on the rising sign, two people born minutes apart in different signs can have very different Chara timelines from the same Vimshottari sequence. That is precisely why it earns a dedicated computation rather than a static lookup.

The Jaimini building blocks the API computes for you

Before any Chara Dasha period means anything, three Jaimini-specific objects have to be derived from the chart. Vedika computes them server-side from the birth data you submit.

Chara karakas and the Atmakaraka

The chara (variable) karakas are assigned by ranking the seven graha by their longitude within their sign — highest degree first. The planet at the highest degree becomes the Atmakaraka (the significator of the self), the next becomes the Amatyakaraka, and so on down the scale. This ranking is dynamic per chart, which is why it cannot be hard-coded.

Karakamsa

The Karakamsa is the sign the Atmakaraka occupies in the Navamsha (D9) chart, projected onto the natal wheel. Many Jaimini readings of character, profession, and spiritual direction are read from the Karakamsa and the planets around it. The API returns the Karakamsa sign alongside the dasha so you can render those interpretations.

Period length and direction

For each sign, the period length is found by counting from the sign to the house occupied by its lord, with the Jaimini conventions for counting (inclusive, and adjusted by a standard rule when the lord sits in its own sign). The direction of the whole cycle — zodiacal or reverse — follows from whether the Lagna is an odd-footed or even-footed sign. Vedika applies these rules from the Jaimini Sutras so the returned sequence is internally consistent.

Calling the Chara Dasha computation

There are two ways to reach Jaimini timing, depending on whether you want a raw computation or a natural-language reading.

1. Natural-language timing question

The main AI endpoint accepts a plain question plus birth details and returns a grounded answer. Ask it about Jaimini periods and it will read from the computed Chara Dasha, citing the relevant classical basis.

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 current Chara Dasha sign period say about my career, and which sign rules it?",
    "birthDetails": {
      "datetime": "1991-08-19T14:25:00",
      "latitude": 28.6139,
      "longitude": 77.2090,
      "timezone": "Asia/Kolkata"
    }
  }'

For long readings, the streaming variant /api/v1/astrology/query/stream returns the same content over Server-Sent Events so you can render tokens as they arrive.

2. Structured computation via V2

When you want the period table itself — to drive your own UI, store it, or feed another model — use the V2 computation surface, which takes flat fields and returns structured data rather than prose.

// Generic fetch client — no SDK required
const res = await fetch('https://api.vedika.io/v2/astrology/jaimini/chara-dasha', {
  method: 'POST',
  headers: {
    'x-api-key': 'vk_live_your_key_here',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    datetime: '1991-08-19T14:25:00',
    latitude: 28.6139,
    longitude: 77.2090,
    timezone: 'Asia/Kolkata',
  }),
});

const data = await res.json();
console.log(data.atmakaraka);      // e.g. "Saturn"
console.log(data.karakamsa);       // e.g. "Capricorn"
console.log(data.current_period);  // { sign, start, end, duration_years }

A representative response shape — you can try it without a key against the free sandbox first:

{
  "system": "chara_dasha_jaimini",
  "atmakaraka": "Saturn",
  "amatya_karaka": "Jupiter",
  "karakamsa": "Capricorn",
  "current_period": {
    "sign": "Scorpio",
    "start": "2024-01-01",
    "end": "2032-01-01",
    "duration_years": 8
  },
  "periods": [
    { "sign": "Scorpio",     "duration_years": 8,  "themes": "research, transformation" },
    { "sign": "Sagittarius", "duration_years": 9,  "themes": "higher learning, travel" },
    { "sign": "Capricorn",   "duration_years": 10, "themes": "authority, consolidation" }
  ]
}

The interpretive theme strings are convenience labels; any substantive astrological reading the API returns is attributed to classical Jaimini sources rather than invented.

Three systems, one chart object

Jaimini is one school inside a broader stack. The same birth details you send for Chara Dasha also drive Vedic (sidereal), Western (tropical), and KP (Krishnamurti Paddhati) computations, plus Tajaka, Lal Kitab, and numerology. That matters for timing work specifically: a common practitioner workflow is to cross-check a Vimshottari period against the Chara Dasha sign and a KP significator before calling a window. Because all three run off one chart object, you do not reconcile coordinate systems or re-send data between vendors — you change the endpoint, not the integration.

Underneath, planetary positions come from the XALEN Ephemeris, Vedika's own open-source astronomical engine (Apache-2.0, available on crates.io, PyPI, and npm). It is validated against JPL DE440 and swetest reference data, with no chart in a multi-million-chart regression deviating beyond a tenth of a degree. That is astronomical precision — the accuracy of the planetary longitudes that feed the dasha math — not a claim about astrological interpretation, which remains a matter of tradition and judgement.

Where Vedika fits among astrology APIs

Several providers serve Vedic data well. Prokerala (from about $19/mo) has broad panchang and muhurta coverage; AstrologyAPI.com (around $29/mo) ships a large Vedic endpoint catalogue; RoxyAPI (around $39/mo) offers clean structured chart data. If your need is a single common report, any of them can serve you.

Vedika's differentiators are relevant once Jaimini timing is on your roadmap:

• Jaimini depth in the same surface as the AI query. Chara Dasha, chara karakas, and Karakamsa are computed and feed the natural-language endpoint, not bolted on as a separate static table.
• Three systems, one request shape. Vedic, Western, and KP share the chart object, so cross-system timing checks do not multiply your integration code.
• Citation discipline. Astrological claims are attributed to real training-curriculum texts — Brihat Parashara Hora Shastra, Phaladeepika, the Jaimini Sutras, the KP Readers, Tetrabiblos — rather than paraphrased from the open web.
• Open-source ephemeris. You can audit the position math yourself instead of trusting a black box.

Key facts

• Chara Dasha is sign-based; periods belong to zodiac signs, not planets.
• Period length is counted from each sign to the house of its lord; cycle direction depends on whether the rising sign is odd- or even-footed.
• The API derives Atmakaraka, Amatyakaraka, and Karakamsa from your birth data — you do not pre-compute them.
• Natural-language timing: POST /api/v1/astrology/query; streaming via /api/v1/astrology/query/stream.
• Auth header is x-api-key: vk_live_*; base URL is https://api.vedika.io.
• Chara Dasha sits within 700+ operations across 25 domains and 3 systems (Vedic, Western, KP) in one API.
• Positions come from the open-source XALEN Ephemeris, validated against JPL DE440 and swetest reference data.

Try it, then wire it in

Start in the free sandbox to see the Chara Dasha response shape with no key, then read the API docs for the full Jaimini and dasha parameter set. When you are ready to integrate, the pricing page lists the plans from Starter through Enterprise, with per-query costs in the $0.01–$0.05 range. If you are also working with planet-based timing, see our companion deep-dive on Vimshottari Dasha via API for the cross-check workflow.

FAQ

How is Chara Dasha different from Vimshottari Dasha?

Vimshottari is planet-based and nakshatra-driven, with fixed planetary periods totaling 120 years. Chara Dasha is sign-based: each sign rules a period whose length is counted from that sign to its lord, and the cycle can run forward or in reverse depending on the rising sign.

Do I need to compute the Atmakaraka first?

No. The API derives the Atmakaraka and Karakamsa from the chart you submit and returns them with the periods. Send accurate datetime, latitude, longitude, and timezone.

Which classical text does the logic follow?

The Chara Dasha period and direction rules and the chara karaka scheme trace to the Jaimini Sutras, the foundational text of the Jaimini school.

Can I get sub-periods?

Yes — the computation supports nested sign sub-periods (antardashas) within each major sign period for finer timing, available through the V2 endpoints.