Skip to content
Lumindocs
UseBuildChangelog
Open Lumin
All tools

Advanced techniques

Bhrigu Bindu (Destiny Point)

get_bhrigu_bindu

Bhrigu Bindu = midpoint of natal Moon and Rahu, a karmic destiny point that activates strongly when transited by slow planets (Saturn, Jupiter, Rahu, Ketu). Returns BB's longitude, sign, house, star/sub lord, and a chronological list of upcoming slow-planet crossings over BB across the next N years (default 10). Modern KP / cross-system; framed as karmic windows, not deterministic events.

Parameters

NameTypeRequiredDescription
birth_datetimestringYesBirth date and time in ISO 8601 format (e.g., "1990-05-15T14:30:00").
latitudenumberYesBirth location latitude. Range: -90 to 90.
longitudenumberYesBirth location longitude. Range: -180 to 180.
utc_offset_minutesnumberYesUTC offset in minutes (e.g., 330 for IST, -300 for EST).
ayanamsaenum: kp | lahiri | raman | true_chitraNoAyanamsa system. Defaults to kp.
query_datestringNoISO date to begin scan from (default: now).
scan_yearsnumberNoYears forward to scan (default: 10).

Example call

Send the request as a standard MCP tools/call:

http
POST https://mcp.lumin.guru/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_bhrigu_bindu",
    "arguments": {
      "birth_datetime": "1992-08-14T04:32:00",
      "latitude": 6.927,
      "longitude": 79.861,
      "utc_offset_minutes": 330,
      "ayanamsa": "kp"
    }
  }
}

Engine endpoint

This tool delegates to the kp-engine endpoint:

http
POST /v1/kp/bhrigu-bindu

The engine is a private internal service. All public access flows through the MCP server, which handles auth, rate limiting, and response compaction.

Birth data

This tool requires birth data. If you have already called set_birth_profile in the same conversation, the MCP server injects those fields automatically and you can omit them from the call.