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 tools that need the exact birth time (no sunrise fallback). Required fields: date, time, lat, lon. Optional fields: person_name, timezone, ayanamsa.
response_format	enum: markdown, json	no	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.
house_number	integer/null	no	House number 1-12. Omit to cover all twelve houses.

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 keeps that one house in significators{} (the server returns all twelve; the tool filters). Values outside 1..12 are refused locally as MCP INVALID_PARAMS. 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 1..12; omit for all twelve.

Output contract

data.ayanamsa (string — 'kp')
data.significators{} — keys '1'..'12':
house (int)
sign_lord (string)
occupants[] (string array — planets in the house, cusp to cusp)
nak_of_occupants[] (string array)
nak_of_lord[] (string array)
all_significators[] (string array — union; not a ranking)
strength_order[] (string array — strongest first: star of occupants, occupants, star of sign lord, sign lord)
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):
— house_number outside 1..12.

INVALID_PARAMS (upstream):
— Birth inside the polar circles, where Placidus cusps do not exist → 422 validation_error, surfaces as MCP INTERNAL_ERROR with the API message.

INTERNAL_ERROR:
— Any upstream API failure or timeout → MCP INTERNAL_ERROR

Edge cases:
— Filtering to one house still returns planet_significators{} for context.
— Inside the polar circles (beyond ~66.5°) Placidus cusps do not exist and the API returns 422 validation_error with details[].issue = no_quadrant_houses_at_this_latitude and input_format_ok = true. This is not an input error: tell the user KP cannot be cast for that place and time; do not ask them to correct their details.

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.