KP Chart
asterwise_get_kp_chart
Builds a KP natal chart with sub-lords on grahas and twelve cusps from BirthData using the KP ayanamsa in the response.
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
Krishnamurti Paddhati charting: lagna row, planet rows with nakshatra_index and sub_lord, house_cusps with matching lords. Recommend BirthData.ayanamsa='kp' for coherent physics — any enum value is accepted locally and forwarded. Accurate birth time matters; midnight placeholder yields unreliable sub-lords for event timing. Not radix (asterwise_get_natal_chart) nor prashna (asterwise_get_prashna_chart).
Workflow
BEFORE: RECOMMENDED — cross-check birth record before trusting sub-lords.
AFTER: asterwise_get_kp_significators — house-level significator chains.
Input
ayanamsa choice is not forced locally — mismatched settings still post to upstream. time='00:00' is accepted without warning.
Output contract
data.ayanamsa (string — 'kp')
data.lagna:
rashi (string)
rashi_index (int)
longitude (float)
nakshatra_lord (string)
sub_lord (string)
data.planets{} — Sun..Ketu:
longitude (float)
rashi_index (int)
rashi (string)
degree (float)
is_retrograde (bool)
house (int)
nakshatra_index (int — 0–26)
nakshatra_lord (string)
sub_lord (string)
data.house_cusps{} — keys '1'..'12':
longitude (float)
rashi_index (int)
rashi (string)
nakshatra_lord (string)
sub_lord (string)
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:
— Sub-lord chains degrade when true birth time unknown.
Do not confuse with
asterwise_get_natal_chart — classical bundle without KP sub-lords.
asterwise_get_kp_ruling_planets — live moment rulers, not natal cusps.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.