get_transits
Use the contract field `natalChart` to submit the underlying bodygraph data, then request current or dated transit context. The literal identifier is preserved for API compatibility.
Developer outcome: Build time-aware agent experiences without calculating planetary positions in the client.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
date | string (local wall time) | Yes | Explicit transit moment as a local wall clock time in the supplied timezone, with no Z and no UTC offset. MCP requires it so a keyed retry addresses the same instant. It may be in the future. |
timezone | string | No | IANA timezone for the transit moment. |
natalChart | object | No | Optional bodygraph birth input with birthDateTime and timezone. birthDateTime is a local wall clock time with no Z and no UTC offset. The field name is part of the backend contract. |
idempotencyKey | string | Yes | Stable key for this intended transit calculation. Reuse it only with identical arguments when retrying. |
Birth times are local wall clock times. Send the birth date and time as it read on the clock where the person was born, with no Z and no UTC offset, and give the timezone separately as an IANA identifier. "birthDateTime": "1990-05-15T14:30:00" with "timezone": "America/New_York" means half past two in the afternoon in New York.
Deprecated: Values ending in Z or a numeric offset are deprecated. The MCP forwards them and the API still accepts them for now, reading them as UTC, and the deprecation is announced on the API response. They will stop being accepted, and the date will be announced in advance. Read the full rule.
Request
Sanitized JSON-RPC
{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "get_transits",
"arguments": {
"date": "2026-08-06T12:00:00",
"timezone": "UTC",
"natalChart": {
"birthDateTime": "1990-05-15T14:30:00",
"timezone": "America/New_York"
},
"idempotencyKey": "transits-2026-08-06-v1"
}
}
}Success response shape
- Transit planetary positions
- Activated gates and channels
- Connections to the supplied bodygraph input
The response also includes tier and quota metadata supplied by the API entitlement layer. Exact domain fields vary by tool and requested detail level.
Errors
- Startup tier required
- Invalid bodygraph input
- Invalid transit date
- Quota exceeded
Quota behavior
After input validation, authorization, and tier checks pass, an execution attempt that reaches the calculation provider consumes exactly one shared API unit—even if a later presentation step fails. Malformed or ambiguous input, denied tiers, unknown references, and other pre-provider failures consume zero. Check current usage at my.humandesign.ai.