HumanDesign.ai Agent HTTP API reference
Overview
Agent HTTP exposes the same six calculation and reference operations as HTTP endpoints. Use it when your application wants named HTTP calls instead of the MCP protocol.
Base path: https://api.humandesign.ai/agent/v1/tools
Authentication
Every request uses either Authorization: Bearer YOUR_HDAI_API_KEY or X-Api-Key: YOUR_HDAI_API_KEY. Query-string credentials are not supported.
Endpoints
| Method | Path | Purpose |
|---|---|---|
| POST | /resolve-timezone |
Resolve a location to timezones and geographic metadata. |
| POST | /generate-chart |
Generate a natal chart. |
| POST | /generate-composite-chart |
Generate a two-person composite chart. |
| POST | /get-reference-item |
Read a gate, channel, center, or profile record. |
| POST | /get-transits |
Get a forecast or natal-versus-transit response. |
| POST | /search-celebrities |
Search the public-figure catalog. |
Response format
Successful responses use a versioned envelope:
{
"version": "v1",
"tool": "generate_chart",
"data": {},
"meta": {},
"error": null
}The meta object includes request and quota information. Treat response fields as structured data; do not parse the summary text as the source of truth.
Access and quota
The API checks entitlement before running an operation. A successful request consumes one shared API unit. Your available operations and limits depend on your current API tier; retrieve current availability through the authenticated MCP catalog or your account tools rather than relying on a copied pricing table.