KP Significators
asterwise_get_kp_significators
Computes KP significator chains for all houses or one optional house from BirthData and returns house tables plus planet-tier reverse indexes.
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 | |
house_number | integer/null | no |
What it covers
For each house string key '1'..'12', lists sign_lord, occupants, nakshatra lord chains, and unions; planet_significators{} exposes tiered house lists per graha. Optional house_number filters upstream when provided. Out-of-range house integers are not validated locally — upstream handles errors as MCP INTERNAL_ERROR. Requires same birth tuple as asterwise_get_kp_chart for coherent analysis.
Workflow
BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators.
AFTER: None.
Input
house_number optional int; omit for all twelve. Values outside 1..12 are validated upstream only.
Output contract
data.ayanamsa (string — 'kp')
data.significators{} — keys '1'..'12':
house (int)
sign_lord (string)
occupants[] (string array)
nak_of_occupants[] (string array)
nak_of_lord[] (string array)
all_significators[] (string array)
data.planet_significators{} — per planet:
tier1_houses[] (int array)
tier2_houses[] (int array)
tier3_houses[] (int array)
tier4_houses[] (int array)
all_significators[] (int array)
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 — house_number not bounds-checked here.
INVALID_PARAMS (upstream):
— None — invalid house indices surface as MCP INTERNAL_ERROR at the tool layer.
INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR
Edge cases:
— Filtering to one house still returns planet_significators{} for context.
Do not confuse with
asterwise_get_kp_chart — cusps and sub-lords, not tiered significator unions.
asterwise_get_natal_chart — classical drishti matrices differ from KP significator tiers.
Connect
Remote MCP endpoint: https://mcp.asterwise.com/mcp. Authenticate with Authorization: Bearer <API key> or OAuth. See the MCP setup guide.