:::note **TL;DR** - A production Human Design API must return the complete bodygraph in one call: type, strategy, inner authority, profile, definition, incarnation cross, all nine centers, the defined channels, and all 26 gate activations. - Two accuracy checks separate correct charts from plausible wrong ones: the Design side solved on the exact 88 degree solar arc, and true lunar nodes rather than mean nodes. - RoxyAPI ships all of it behind one key, with a Remote MCP server for AI agents, localized responses, and flat request based pricing across 12 domains. ::: Every Human Design app stands on the same foundation: a chart engine that turns a birth moment into a bodygraph. Most teams should not build that engine. The math spans a solar arc solver, planetary ephemerides, 64 gates, 36 channels, and a strict authority hierarchy, and one wrong choice deep in the stack produces charts that look right and read wrong. Choosing a Human Design API is therefore a due diligence problem, not a shopping problem. This guide is the evaluation checklist: what a complete bodygraph response must contain, the accuracy traps that silently corrupt charts, the endpoints real products need beyond the natal chart, how AI agents consume the data, and which pricing models punish growth. Run every check against any vendor, including RoxyAPI. ## What should a Human Design API return in one call? A production Human Design API returns the complete bodygraph from one request carrying only a birth date, time, and timezone: the energy type, strategy, inner authority, signature and not-self theme, profile, definition, incarnation cross, all nine centers with their defined state, every defined channel, and all 26 planetary activations across the Personality and Design sides. Anything less forces you to reassemble a chart from fragments. | Chart object | A complete response contains | What to check | |---|---|---| | Type | One of Manifestor, Generator, Manifesting Generator, Projector, Reflector, with strategy, signature, and not-self theme | Derived from how motors wire to the Throat, never a shortcut table | | Inner authority | One of Emotional, Sacral, Splenic, Ego, Self-Projected, Mental, Lunar | All seven resolvable in strict priority, including Lunar | | Profile | Personality Sun line over Design Sun line, such as 3/5, with keynotes | Both line numbers exposed, not just the label | | Definition | None, Single, Split, Triple Split, or Quadruple Split | Computed from connected components among defined centers | | Incarnation cross | Four cardinal gates, the angle (Right Angle, Juxtaposition, Left Angle), the canonical name | Named crosses, not just gate numbers | | Centers | All nine, with defined state, motor and awareness flags, active gates | Open centers included, not only defined ones | | Channels | Every defined channel with name and circuit family (Individual, Collective, Tribal) | The two connected centers listed per channel | | Activations | 26 total, 13 Personality and 13 Design, with planet, gate, line, and the matching I-Ching hexagram | The 13 classical gate-bearing bodies only | Fragmentation is the first red flag. If type, centers, channels, and activations arrive from separately billed endpoints, every user chart multiplies your request count and your bill. One call should equal one complete chart. Ready to run these checks against a live endpoint? The [Human Design API](/products/human-design-api "production-ready Human Design API with bodygraph, type, authority, profile, connection, and transit endpoints") from RoxyAPI returns the full bodygraph in a single call, one of 164+ endpoints across 12 insight domains on one key. [See pricing](/pricing "RoxyAPI pricing and plan tiers"). ## How do you verify a Human Design API is accurate? Run three checks before trusting any Human Design API: the planetary positions must be verified against an external authority such as NASA JPL Horizons, the Design side must be solved on the exact 88 degree solar arc rather than approximated as 88 calendar days, and the lunar nodes must be true nodes, not mean nodes. Each failure mode produces charts that look plausible and are wrong. :::stat 88° **Solar arc between the Design Sun and the natal Sun.** The Design moment is the instant the Sun sat exactly 88 degrees of ecliptic longitude before its natal position, roughly 88 days before birth but almost never exactly. RoxyAPI solves for that instant precisely; the calendar day shortcut can push Design activations into a neighboring gate or line. Method details: [methodology](/methodology "how RoxyAPI verifies calculations against NASA JPL Horizons"). ::: Precision matters because the wheel is fine grained: each of the 64 gates spans 5.625 degrees and each line spans 0.9375 degrees, so the Moon crosses a gate in about 10 hours and a line in under 2. RoxyAPI planetary positions show a median difference of 16 arcseconds from NASA JPL Horizons DE441, with the Moon at 3 arcseconds, in the open [astrology-api-benchmark](https://github.com/RoxyAPI/astrology-api-benchmark) dataset anyone can rerun. :::warning **Mean nodes silently flip charts.** The mean and true lunar node diverge by up to about 1.75 degrees, and because the node pair activates two opposite gates at once, a divergence near a gate boundary changes two activations together. On one published reference chart, the mean node places the Personality nodes in gates 40 and 37, completing the 37-40 channel and reporting Emotional authority with a Split definition; the true node places them in gates 64 and 63, and the correct chart is Self-Projected with a Single definition. Professional Human Design software uses the true node. RoxyAPI does the same. Ask any vendor which node their engine uses before you integrate. ::: ## Which endpoints matter beyond the natal bodygraph? A bodygraph generator alone powers a one-screen app. Products that retain users need relationship charts, group analysis, daily movement, and reference data: a connection endpoint for two-person dynamics, Penta for teams, a transit overlay for daily guidance, Variables for the advanced layer, and static gate and center lookups for content pages. RoxyAPI covers all of this with 12 Human Design endpoints. | Endpoint | Returns | Powers | |---|---|---| | `POST /human-design/bodygraph` | The complete chart described above | Onboarding, full readings | | `POST /human-design/type` | Type, strategy, authority, signature, not-self, profile | Fast identity lookups | | `POST /human-design/profile` | Profile with both Sun lines and keynotes | Profile features | | `POST /human-design/centers` and `GET /human-design/centers/{id}` | Nine center states; single center reference | Center explainers | | `POST /human-design/channels` | Defined channels with circuit families | Channel analysis | | `POST /human-design/gates` and `GET /human-design/gates/{number}` | All 26 activations; single gate reference | Gate content libraries | | `POST /human-design/connection` | Channels classified as Electromagnetic, Dominance, Compromise, or Companionship, plus combined definition | Dating and relationship apps | | `POST /human-design/penta` | The six Penta channels as strengths or gaps for three to five people | Team and family tools | | `POST /human-design/transit` | Channels the current sky temporarily completes, personal and educational | Daily guidance, notifications | | `POST /human-design/variables` | The four arrows with Color, Tone, Base, direction, and confidence flags | PHS and Rave Psychology readings | The confidence flag on Variables is an honesty signal worth testing. A Tone spans only 0.026 degrees of ecliptic longitude, which the Sun crosses in about 38 minutes of clock time, so a birth time rounded to the quarter hour can flip an arrow. RoxyAPI flags knife-edge arrows as low confidence; a vendor returning Color and Tone with no uncertainty signal is asking you to ship guesses. ## Can AI agents call Human Design data through MCP? Yes, and in 2026 this is a first-class buyer criterion. RoxyAPI exposes Human Design as a Remote MCP server over Streamable HTTP at `/mcp/human-design`, so a deployed agent in Claude, ChatGPT, Gemini, n8n, or Dify calls tools like `post_human_design_bodygraph` directly, with no local server, no Docker, and no stdio wrapper to maintain. The architecture point matters more than the checkbox. With Remote MCP, your agent grounds every reply in verified calculations and answers in your own voice and system prompt: the model never invents a gate, a profile, or an authority. You bring your own LLM instead of renting a hosted chatbot with a hidden prompt. Setup and client coverage live in the [MCP documentation](/docs/mcp "RoxyAPI Remote MCP server setup for Claude, Cursor, ChatGPT, and agent frameworks"). Typed SDKs for TypeScript, Python, PHP, C#, and Go, plus a WordPress plugin, regenerate from the live OpenAPI spec at `/api/v2/human-design/openapi.json`, so new endpoints appear automatically. ## How do you generate a bodygraph from the API? Send a birth date, time, and timezone to the bodygraph endpoint and the complete chart returns in one response. No geocoding step is needed: the bodygraph depends only on ecliptic longitudes, so latitude and longitude are optional, and the timezone field accepts either a decimal UTC offset or an IANA name like America/New_York. :::tabs ### curl ```bash curl -s -X POST https://roxyapi.com/api/v2/human-design/bodygraph \ -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ -d '{"date":"1990-07-15","time":"13:00:00","timezone":-4}' ``` ### JavaScript ```js const res = await fetch('https://roxyapi.com/api/v2/human-design/bodygraph', { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-API-Key': 'YOUR_API_KEY' }, body: JSON.stringify({ date: '1990-07-15', time: '13:00:00', timezone: 'America/New_York' }) }); const chart = await res.json(); ``` ### Python ```python import requests r = requests.post( 'https://roxyapi.com/api/v2/human-design/bodygraph', headers={'X-API-Key': 'YOUR_API_KEY'}, json={'date': '1990-07-15', 'time': '13:00:00', 'timezone': -4}, ) chart = r.json() print(chart['type'], chart['authority'], chart['profile']) ``` ::: This is the real production response for that birth moment, trimmed to one center, one channel, and one activation; the live response returns all nine centers, every defined channel, and all 26 activations: ```json { "type": "Projector", "strategy": "Wait for the invitation", "authority": "Emotional", "signature": "Success", "notSelf": "Bitterness", "profile": "3/5", "definition": "Split", "incarnationCross": { "gates": [62, 61, 42, 32], "angle": "Right Angle", "angleCode": "RAX", "name": "Right Angle Cross of Maya 2" }, "centers": [ { "id": "throat", "name": "Throat", "defined": true, "motor": false, "awareness": false, "theme": "Consistent expression and the ability to manifest through speech and action when connected to a motor.", "gates": [12, 31, 62] } ], "channels": [ { "gateA": 7, "gateB": 31, "name": "The Alpha", "circuit": "Collective", "centers": ["g", "throat"] } ], "gates": [ { "planet": "Sun", "side": "personality", "gate": 62, "line": 3, "gateName": "Detail", "ichingHexagram": { "number": 62, "english": "Preponderance of the Small" } } ] } ``` The same endpoints localize with a query parameter. `POST /human-design/type?lang=de` for the same birth returns, captured live: ```json { "type": "Projektor", "strategy": "Auf die Einladung warten", "authority": "Emotional", "signature": "Erfolg", "notSelf": "Bitterkeit", "profile": "3/5" } ``` Test [`POST /human-design/bodygraph`](/api-reference#tag/human-design/POST/human-design/bodygraph "live Human Design bodygraph endpoint reference with request and response schemas") in the interactive reference: the playground returns real production responses, so you audit the output before paying for anything. ## How should a Human Design API be priced and licensed? Prefer flat request based pricing: one request equals one quota unit, whatever you call. Credit-wallet models weight a full bodygraph heavier than a gate lookup, which quietly taxes your most valuable feature. On RoxyAPI, the Starter plan is $39 per month for 25,000 requests across all 12 domains, about $3.25 per domain, and a Human Design chart costs exactly one unit like everything else. Licensing is the quieter criterion. Ask what engine the vendor wraps: calculators built over Swiss Ephemeris inherit AGPL copyleft considerations in some architectures, while RoxyAPI runs Roxy Ephemeris, built from the ground up and verified against NASA JPL Horizons, with no AGPL restrictions on what you build. The honest counterpoint: if you need one static feature, have Human Design expertise in house, and accept the licensing and verification burden, building your own engine can win. The hard costs land in the exact solar arc solver, true node handling, the authority priority chain, and proving your output against published charts, and that is where the months go. ## FAQ **What is the best Human Design API for developers?** RoxyAPI is the strongest choice for production apps because it returns the complete bodygraph in one call: type, authority, profile, definition, incarnation cross, centers, channels, and all 26 activations. The Design side is solved on the exact 88 degree solar arc, nodes are true nodes, and positions are verified against NASA JPL Horizons. The same key unlocks a Remote MCP server, typed SDKs, and 11 more insight domains on one flat plan. **Do I need the birth location to calculate a Human Design chart?** No. The bodygraph is derived from the birth date, time, and timezone, because gate activations depend only on ecliptic longitudes. RoxyAPI accepts the timezone as a decimal UTC offset or an IANA name such as America/New_York, so there is no geocoding call and no location database to wire up. **Can a Human Design API calculate compatibility between two people?** Yes. The RoxyAPI connection endpoint takes two birth moments and classifies every connected channel as Electromagnetic, Dominance, Compromise, or Companionship, alongside the combined definition and which person defines each center. For groups of three to five people, the Penta endpoint reports the six Penta channels as defined strengths or gaps. **How precise does the birth time need to be for a Human Design chart?** Minutes matter. Each line spans 0.9375 degrees, the Moon crosses a line in under 2 hours, and the Sun crosses a Tone boundary in about 38 minutes, so a rounded birth time can shift a profile line or flip a Variable arrow. RoxyAPI returns a per-arrow confidence flag on the Variables endpoint that turns false near a Color or Tone boundary instead of presenting a knife-edge value as fact. **Is there a Human Design MCP server for AI agents?** Yes. RoxyAPI runs a Remote MCP server at /mcp/human-design over Streamable HTTP, so deployed agents in Claude, ChatGPT, Gemini, n8n, or Dify call bodygraph, connection, transit, and gate tools with an API key and no local setup. The agent grounds its answers in verified calculations rather than inventing chart details. ## Conclusion Choosing a Human Design API comes down to completeness in one call, verifiable accuracy on the 88 degree solar arc and the lunar nodes, endpoint coverage beyond the natal chart, agent readiness, and pricing that does not punish your best feature. Run this checklist against the [Human Design API](/products/human-design-api "Human Design API with full bodygraph, connection, Penta, transit, and Variables endpoints") from RoxyAPI: the live playground returns real production responses, so every check takes minutes, and one subscription covers all 12 domains.