HumanDesign.ai API access and quota

One entitlement system across API surfaces

REST, Agent HTTP, and the API-key MCP catalog use the same API entitlement and monthly calculation quota. A valid key alone does not guarantee that every operation is available.

Current access levels

Tier	Monthly Quota	Includes
Free	100	Creator feature set with a lower monthly allowance.
Creator	10,000	Core chart, composite, location, and reference operations.
Startup	100,000	Creator access plus full chart detail, transits, returns, and forecast operations.
Business	1,000,000	Startup access plus calendar, public-figure, streaming, webhook, and batch operations.
Enterprise	Custom	Business-level access with commercial terms managed separately.

Your exact usage, remaining quota, and reset date are also returned by authenticated API responses.

When quota is used

• A successful REST, Agent HTTP, or MCP tool execution consumes one shared API unit.
• MCP discovery requests such as initialize, notifications/initialized, ping, and tools/list do not consume quota.
• Invalid input, unknown MCP tools, invalid credentials, inactive access, and insufficient-tier requests do not consume quota.

Common response statuses

• 400: the request input is invalid.
• 401: no usable API key was provided.
• 403: the key is not allowed to use the requested operation.
• 429: the available monthly quota is exhausted.

Keep account access separate from API plans

OAuth access to HumanDesign.ai account-connected features has its own membership, ownership, workspace, and permission rules. It does not bypass API-key entitlement checks, and an API-key plan does not grant access to another person’s account data.