Char Dasha
asterwise_get_char_dasha
Computes Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
birth | object | yes | Birth data for a single person. Fields: date, time, lat, lon*, person_name, timezone, ayanamsa |
response_format | enum: markdown, json | no |
What it covers
Uses the classical system where rashis (not grahas) rule time periods, including Atmakaraka, eight karakas, current Maha/Antar labels in Sanskrit signs, and a period array with nested antardashas. It does not return Vimshottari (asterwise_get_dasha), Yogini, or Ashtottari timelines.
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords.
AFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native.
Input
Period start_date and end_date in data.periods[] are YYYY-MM-DD (ISO), unlike asterwise_get_dasha which uses DD/MM/YYYY in its tree. All other parameters follow the BirthData global contract.
Output contract
data.atmakaraka (string — planet name)
data.start_rashi (string — Sanskrit rashi name)
data.start_rashi_index (int)
data.karakas{} — object mapping classical karaka keys to planet names
data.current_mahadasha (string — Sanskrit rashi name, e.g. 'Mithuna')
data.current_antardasha (string — Sanskrit rashi name)
data.periods[] — Mahadasha objects:
rashi (string)
rashi_index (int)
years (int)
start_date (string — YYYY-MM-DD ISO)
end_date (string — YYYY-MM-DD ISO)
antardashas[] — same shape as one level (no further nesting)
Response format
response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode.
Compute class
MEDIUM_COMPUTE
Errors
INVALID_PARAMS (local — caught before upstream call):
None — all validation is upstream.
INVALID_PARAMS (upstream):
— None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Two planets at the same degree: classical tie-break rules apply upstream; no separate error.
Do not confuse with
asterwise_get_dasha — Vimshottari planet lords with DD/MM/YYYY in periods[], not sign-based Char Dasha.
asterwise_get_yogini_dasha — eight Yoginis and data.periods.root[], not classical signs.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.