Ashtakavarga
asterwise_get_ashtakavarga
Computes full Ashtakavarga bindu matrices, trikona and ekadhipatya reductions, and sarva totals from BirthData for transit support analysis.
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
Ashtakavarga: bhinna tables per contributing body (including Lagna), reduced variants, sarva and sarva_reduced arrays, after_trikona/after_ekadhipatya aggregates, birth_time_provided flag. Threshold lore: twenty-eight or more sarva bindus supports transits; below twenty-five implies friction. Not Shadbala totals (asterwise_get_chart_strength) though that bundle duplicates this data when needed.
Workflow
BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before AVK study.
AFTER: asterwise_get_gochar — uses AVK scores in transit rows.
Input
BirthData only.
Output contract
data.bhinna — keys Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Lagna → each twelve-element int array (rashi index 0=Mesha .. 11=Meena), bindu 0..8
data.bhinna_after_trikona — seven planets (no Lagna), same array shape
data.bhinna_after_ekadhipatya — same after further reduction
data.sarva[] — twelve ints
data.sarva_reduced[] — twelve ints
data.after_trikona[] — twelve ints
data.after_ekadhipatya[] — twelve ints
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
Errors
INVALID_PARAMS (local — caught before upstream call):
None — BirthData Pydantic only.
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:
— Rahu/Ketu are not classical bhinna contributors per tradition.
Do not confuse with
asterwise_get_chart_strength — primary payload is Shadbala/Vimshopaka, though it embeds AVK too.
asterwise_get_gochar — applies AVK scores to transits rather than exposing raw matrices.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.