Ashtottari Dasha
asterwise_get_ashtottari_dasha
Computes the 108-year Ashtottari Dasha tree with configurable depth (levels 1–5) and returns periods under data.periods.root with DD/MM/YYYY dates.
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 | |
levels | integer | no |
What it covers
Provides the Ashtottari planetary sequence (eight grahas, Ketu excluded) with the same levels semantics as Vimshottari: deeper levels nest sub-periods in sub[]. Classical texts restrict use when Rahu is in Kendra/Trikona from Lagna lord (not in Lagna); this tool always returns a full timeline with no niyama_met flag — apply rules externally. It is not Vimshottari, Yogini, or Char Dasha.
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing between Ashtottari and Vimshottari.
AFTER: asterwise_get_dasha — optional Vimshottari comparison.
Input
levels: same as asterwise_get_dasha (1–5), enforced locally before the API call. Periods use data.periods.root[], not data.periods[]. Dates in periods are DD/MM/YYYY.
Output contract
data.periods.root[] — Mahadasha objects:
planet (string)
start_jd (float)
end_jd (float)
start_date (string — DD/MM/YYYY)
end_date (string — DD/MM/YYYY)
sub[] — Antardasha objects, same shape, nested per levels
data.birth_time_provided (bool)
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 (timing scales with levels similarly to asterwise_get_dasha)
Errors
INVALID_PARAMS (local — caught before upstream call):
— levels < 1 or levels > 5 → MCP INVALID_PARAMS
INVALID_PARAMS (upstream):
None — remaining validation is upstream.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— No classical applicability check in the response; full timeline is always returned.
Do not confuse with
asterwise_get_dasha — standard 120-year Vimshottari with data.periods[], not Ashtottari or data.periods.root[].
asterwise_get_yogini_dasha — 36-year Yogini cycle with yogini names on each row.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.