Human Design API Overview
APIUpdated Mar 12, 20262 min read
Overview
The HumanDesign.ai API now ships in three surfaces that share the same membership billing system:
- Legacy REST for direct endpoint integrations.
- Agent HTTP at
https://api.humandesign.ai/agent/v1/tools/*for action clients. - MCP at
https://api.humandesign.ai/mcpfor tool-based AI workflows.
All three surfaces use the same API key and the same monthly PMPro quota.
Authentication
Legacy REST supports X-Api-Key headers and the api_key query parameter. Agent HTTP and MCP require header authentication only:
X-Api-Key: your_api_key_here
Authorization: Bearer your_api_key_here
Query-string API keys are rejected on /agent/v1 and /mcp.
Tier-Aware Access
| Tier | REST Access | Agent / MCP Access |
|---|---|---|
| Creator | Core charts, composites, library, locations | resolve_timezone, generate_chart (core), generate_composite_chart, get_reference_item |
| Startup | Creator + enhanced charts, transits, return charts | Creator tools + generate_chart (full) and get_transits |
| Business | Startup + calendar, celebrity, webhooks, stream, batch | Startup tools + search_celebrities |
| Enterprise | Full Business access in v1 | Full Business access in v1 |
Billing Rules
- Each successful legacy REST request consumes 1 API unit.
- Each Agent HTTP tool call consumes 1 API unit.
- Each MCP
tools/callrequest consumes 1 API unit. - MCP
initialize,notifications/initialized,ping, andtools/listare checked for entitlement but do not consume usage.
Where to Go Next
- Read How to Get a Human Design API Key for plan and billing details.
- Read HumanDesign.ai MCP Quickstart to connect an MCP client.
- Read Agent HTTP API Reference for the normalized tool endpoints.
- Read API Access Tiers and Billing for the full tier matrix.
