---
title: "Rahu Kalam & Gulika (राहु काल) (羅睺時段)"
method: GET
path: "/api/trpc/rahukalam.day"
tags: ["Indian"]
---

# Rahu Kalam & Gulika (राहु काल) (羅睺時段)

`GET /api/trpc/rahukalam.day`

## Request

- Base URL: `https://api.asktian.com`
- URL: `https://api.asktian.com/api/trpc/rahukalam.day`
- Auth: HTTP bearer

RAHU KALAM, YAMAGANDAM & GULIKA KALAM — the three daily shadowed windows of the South Indian day, consulted before every journey, signing and ceremony from Chennai to Colombo to Singapore: the REAL daylight (sunrise→sunset, from the catalogue's gold-tested solar solver shared with Choghadiya and the Gowri Panchangam) cut into eight equal parts, the weekday assigning one to each kalam — so the familiar 90-minute clock times stretch and shrink with the actual day, as the tradition intends. THE TABLES ARE TWO-WITNESS AND LAW-BOUND at load: the full 21-cell idealized table agrees across independent references AND obeys closed forms — Gulika descends 7..1 Sunday to Saturday, Yamagandam follows ((4−weekday) mod 7)+1, Rahu Kalam (the mnemonic 8,2,7,5,6,4,3) never opens the day, the three windows never collide, and every published idealized cell is reproduced. Gulika's own inversion (avoided for beginnings, held GOOD for death-rites) served as the tradition has it; night variants named, not computed; polar latitudes refused honestly. Returns the three windows in local clock, an optional is-now-inside flag, and the full eight-segment grid. Indian becomes 29. Pure compute, no LLM.

Cost: 1 TIAN Points per call. tRPC procedure `rahukalam.day`.

## Query parameters

- `input` string

## Response `200`

tRPC result envelope

- TrpcResult: tRPC HTTP response envelope.
  - `result` object
    - `data` object: The procedure's return value (system-specific).

---

[API](https://skmtc.dev/asktian/apis/asktian-metaphysics-api.md) · [All operations](https://skmtc.dev/asktian/apis/asktian-metaphysics-api/llms.txt) · [OpenAPI document](https://skmtc.dev/asktian/apis/asktian-metaphysics-api/revisions/3c8fdc979206?raw)