Krishnamurti Paddhati (KP) sub-lord lookup¶
KP refines Vimshottari's nakshatra-based timing by chopping each nakshatra (13°20′ = 800′) into 9 sub-divisions in proportion to the Vimshottari years. Each sub is in turn split into 9 sub-subs, giving a 0.05° resolution timing grid.
For any sidereal longitude L the KP triplet is
(nakshatra-lord, sub-lord, sub-sub-lord). KP prediction focuses
heavily on the sub-sub-lord — every house cusp and every transit
point can be classified by it.
GET /v1/vedic/kp/lookup¶
Chart-independent. Pass any sidereal longitude in [0, 360)
degrees and receive the full KP decomposition.
curl -H "Authorization: Bearer $TOKEN" \
"https://api.astrolinkers.com/v1/vedic/kp/lookup?longitude_deg=125.5"
{
"longitude_deg": 125.5,
"rashi": "leo",
"nakshatra": "Magha",
"pada": 1,
"nakshatra_lord": {"lord": "ketu", "start_deg": 120.0, "end_deg": 133.333},
"sub_lord": {"lord": "ketu", "start_deg": 120.0, "end_deg": 120.778},
"sub_sub_lord": {"lord": "venus", "start_deg": 120.0, "end_deg": 120.130}
}
How sub-divisions are sized¶
Each Vimshottari lord owns a chunk of the nakshatra in proportion to its years:
| Lord | Years | Slice of nakshatra |
|---|---|---|
| Ketu | 7 | 7 / 120 × 13.333° = 0.778° |
| Venus | 20 | 20 / 120 × 13.333° = 2.222° |
| Sun | 6 | 0.667° |
| Moon | 10 | 1.111° |
| Mars | 7 | 0.778° |
| Rahu | 18 | 2.000° |
| Jupiter | 16 | 1.778° |
| Saturn | 19 | 2.111° |
| Mercury | 17 | 1.889° |
The 9 sub-divisions walk the Vimshottari ring starting from the nakshatra's own lord (so Ashwini, owned by Ketu, starts with a Ketu sub-slice).
Sub-subs repeat the same algorithm within each sub: the sub starts with the sub's lord, then walks the ring.
Typical KP workflows¶
- House-cusp sub-lord — pick each house cusp longitude (from
/bhava-chakra), feed into/kp/lookup, and classify each house by its sub-sub-lord. Houses sharing a sub-sub-lord move together under that lord's dasha. - Transit timing — for an exact event (eclipse, station, ingress), the sub-sub-lord pinpoints which planet's promised results activate.
KP itself is its own full predictive framework; this endpoint exposes the foundational lookup math so callers can build deeper KP analyses without re-implementing the Vimshottari-proportion split.