API Access Tiers and Billing
APIUpdated Mar 12, 20261 min read
Tier Mapping
HumanDesign.ai enforces plan access by tier, not just by whether an API key is valid.
| Tier | PMPro Level | Quota | Summary |
|---|---|---|---|
| Creator | 18 | 1,000 / month | Core charts, composites, library, locations |
| Startup | 17 | 10,000 / month | Creator + enhanced charts, transits, returns |
| Business | 20 | 100,000 / month | Startup + calendar, celebrity, webhooks, streaming, batch |
| Enterprise | 19 | Custom | Full Business access in v1 with custom agreements |
Legacy REST Tier Rules
- Creator:
/hd-data,/hd-data-composite,/v2/hd-data-composite,/group-composite,/locations,/library/* - Startup:
/v2/hd-data,/v3/hd-data,/hd-data-transit,/planetary-positions,/planetary-forecast,/solar-return,/lunar-return,/saturn-return,/chiron-return,/progressed-chart - Business:
/gate-calendar,/transit-alerts,/moon-phases,/ical-export,/celebrity/search,/celebrity/{slugOrId},/webhooks/*,/stream/planetary-positions,/batch/charts
Billing Behavior
- REST requests consume usage after the entitlement check passes.
- Agent HTTP requests consume usage after the entitlement check passes.
- MCP
tools/callrequests consume usage after the entitlement check passes. - MCP
initialize,notifications/initialized,ping, andtools/listare free. - Insufficient tier does not consume quota.
- Invalid keys and inactive memberships do not consume quota.
Error Semantics
401= missing API key403= invalid key or insufficient tier429= monthly quota exhausted400= invalid request parameters
Shared Quota Reminder
You do not purchase separate MCP credits. The same plan quota covers legacy REST, Agent HTTP, and MCP.
