# Human Design API

> Generate the full Human Design bodygraph from a birth moment: type, strategy, inner authority, profile, definition, incarnation cross, the nine centers, defined channels, and all 26 gate activations. Planetary positions verified against NASA JPL Horizons, the Design side solved on the exact 88 degree solar arc. One key, remote MCP, typed SDKs, 10 endpoints.

Ship a Human Design bodygraph your users can trust. This week.

- Product page: https://roxyapi.com/products/human-design-api
- OpenAPI spec: https://roxyapi.com/api/v2/human-design/openapi.json
- Remote MCP server: https://roxyapi.com/mcp/human-design
- Authentication: `X-API-Key` header on every request
- Pricing: https://roxyapi.com/pricing (all domains included in every plan)

## Stats

- latency: <50ms
- uptime: 99.9%
- endpoints: 10

## Features

- Full bodygraph in one call: energy type, strategy, inner authority, signature, not-self theme, profile, definition, and incarnation cross from a single birth date, time, and timezone
- All five energy types derived from the graph: Manifestor, Generator, Manifesting Generator, Projector, and Reflector, with strategy and signature for each
- Seven inner authorities resolved in strict priority: Emotional, Sacral, Splenic, Ego, Self-Projected, Mental, and Lunar
- The 26 gate activations split into 13 conscious Personality and 13 unconscious Design, each enriched with its gate keynote and matching I-Ching hexagram
- The nine centers reported as defined or open with motor and awareness flags, theme text, and the active gates that sit in each
- The 36 channels with circuit family, returning only the defined channels that wire the bodygraph together
- Profile from the two Sun lines with line keynotes, plus definition computed from connected components among defined centers
- Static gate and center lookups for reference UIs, with the Design moment solved on the 88 degree solar arc rather than approximated as 88 calendar days
- Transit overlay that maps the current planetary positions onto a natal bodygraph and reports the channels the transit temporarily completes, split into personal and educational, with the centers they define

## Use Cases

- Spiritual and self-discovery apps: full bodygraph generation, type and authority readings, and profile insights for personal growth journeys
- Dating and relationship platforms: type, authority, and profile compatibility context derived from two birth charts
- AI chatbots and coaching assistants: bodygraph data via remote MCP tool calls for Human Design conversations and decision-making guidance
- Practitioner and reading tools: activation columns, defined channels, and center analysis for professional Human Design charts
- Wellness and mindfulness platforms: strategy and authority prompts that help users make aligned decisions
- Content and editorial platforms: gate and center reference lookups for explainer pages and structured Human Design libraries

## Endpoints

- `POST /api/v2/human-design/bodygraph` Generate full Human Design bodygraph - Type, authority, profile, centers, channels, gates
- `POST /api/v2/human-design/connection` Calculate Human Design connection chart - Two-person composite bodygraph compatibility
- `POST /api/v2/human-design/transit` Generate Human Design transit overlay - Current planetary activations on a natal bodygraph
- `POST /api/v2/human-design/type` Calculate Human Design type, authority and profile
- `POST /api/v2/human-design/gates` Calculate the 26 Human Design gate activations
- `GET /api/v2/human-design/gates/{number}` Look up a Human Design gate by number
- `POST /api/v2/human-design/channels` Calculate the defined Human Design channels
- `POST /api/v2/human-design/centers` Calculate the nine Human Design centers
- `GET /api/v2/human-design/centers/{id}` Look up a Human Design center by id
- `POST /api/v2/human-design/profile` Calculate the Human Design profile and line keynotes

## Example Response

```
POST /api/v2/human-design/bodygraph
```

```json
{
  "type": "Generator",
  "strategy": "Wait to respond",
  "authority": "Emotional",
  "signature": "Satisfaction",
  "notSelf": "Frustration",
  "profile": "1/4",
  "definition": "Triple Split",
  "incarnationCross": {
    "gates": [
      36,
      6,
      11,
      12
    ],
    "angle": "Right Angle",
    "angleCode": "RAX",
    "name": "RAX Cross (36/6/11/12)"
  },
  "centers": [
    {
      "id": "ajna",
      "name": "Ajna",
      "defined": true,
      "motor": false,
      "awareness": true,
      "theme": "A fixed way of processing and conceptualizing. Mental certainty and a consistent thinking style.",
      "gates": [
        11,
        17,
        24
      ]
    }
  ],
  "channels": [
    {
      "gateA": 11,
      "gateB": 56,
      "name": "Curiosity",
      "circuit": "Collective",
      "centers": [
        "ajna",
        "throat"
      ]
    }
  ],
  "gates": [
    {
      "planet": "Sun",
      "side": "personality",
      "gate": 36,
      "line": 1,
      "gateName": "Crisis",
      "ichingHexagram": {
        "number": 36,
        "english": "Darkening of the Light"
      }
    }
  ]
}
```

## MCP Tool Naming

Each REST endpoint has a matching MCP tool on `https://roxyapi.com/mcp/human-design`. Tool name convention is `{http_method_lowercase}_{path_with_slashes_as_underscores_kebab_replaced_with_underscores_braces_stripped}`:

```
POST /human-design/bodygraph                  -> post_human_design_bodygraph
POST /human-design/connection                 -> post_human_design_connection
POST /human-design/transit                    -> post_human_design_transit
```

`tools/list` is free and public (no auth). `tools/call` requires `X-API-Key` (same billing as REST — 1 request per call).

## Error Contract

Success returns clean JSON, no wrapper. Errors return `{ "error": string, "code": string }`. Switch on `code` (stable):

- `validation_error` (400, returns `issues[]` with all field errors at once)
- `api_key_required` (401), `invalid_api_key` (401)
- `subscription_inactive` (403), `subscription_not_found` (404)
- `not_found` (404; PATH-routing 404s carry a fuzzy `suggestion` field)
- `rate_limit_exceeded` (429)
- `internal_error` (500)

Do not retry on 4xx. Do retry on 429 and 5xx with exponential backoff.

## Full Reference

For complete request and response schemas, fetch the OpenAPI spec at https://roxyapi.com/api/v2/human-design/openapi.json. Master agent manifest at https://roxyapi.com/llms.txt. Execution playbook at https://roxyapi.com/AGENTS.md.