HumanDesign.ai gives developers direct API access plus a production remote MCP server. Ship chart generation, practical analysis, comparison, and report workflows through the interface that fits your product, assistant, or agent stack.
Most teams start with one narrow use case, prove value, and then expand into reports, automations, or internal tools.
Generate the chart, summarize it in practical language, and guide the user through their decision style, strengths, and likely friction points.
Personal chart readings in chat
Help users make better choices by translating authority and strategy into timing, process, and risk guidance that an agent can actually use.
Big decision checkpoints
Compare two charts for compatibility, collaboration style, communication patterns, and predictable areas of friction.
Partner and relationship insight
Turn chart and analysis data into polished sections or full reports for personal users, coaches, or premium product experiences.
One-off premium report sections
Bring Human Design into internal tools for role-fit conversations, communication guidance, workshops, and structured people insight workflows.
Internal team insights
All three surfaces connect to the same Human Design engine. The difference is how much orchestration and protocol support you want.
Endpoint
Core API endpointsAuthentication
Shared API key
Best for
Apps and backends that want direct HTTP access and full control over orchestration.
Billing
Uses the shared HumanDesign.ai platform access model.
Endpoint
/agent/v1/tools/*Authentication
Shared API key
Best for
Assistants and workflow tools that want named HTTP tools without full MCP protocol handling.
Billing
Uses the same platform access model as the rest of the API.
Endpoint
https://api.humandesign.ai/mcpAuthentication
Authorization: Bearer <key> or X-Api-Key
Best for
MCP-compatible clients that need tool discovery, resources, prompts, and a standard remote agent protocol.
Billing
Chart and analysis calls follow platform access. Report generation uses AI credits.
Start with a smaller monthly call package, then scale to higher-volume products and team workflows. The same plan supports REST API, Agent HTTP, and Remote MCP.
For prototypes, internal tools, and first customer workflows.
For production assistants, growing products, and recurring usage.
For teams, partner platforms, and higher-volume shipping.
Developers do not need separate products for each interface. Choose the surface that matches the client and keep the same access model as you move from app logic to agent workflows.
Chart and analysis usage follows your plan quota. Report generation uses AI credits where applicable.
More technical detail