# Human Design Compatibility API

> Human Design Compatibility API. Calculate a Human Design connection chart by overlaying two bodygraphs. For each of the 36 channels the dynamic between

- Capability page: https://roxyapi.com/apis/human-design-compatibility-api
- Full domain: 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

## Overview

Calculate a Human Design connection chart by overlaying two bodygraphs. For each of the 36 channels the dynamic between the two people is classified as electromagnetic, dominance, compromise, or companionship, the four mechanics of how two designs meet. Also returns the nine centers as defined or open in the combined bodygraph with which person defines each, the combined definition, and a count of each dynamic. Built for relationship, dating, and coaching tools.

## Endpoints

- `POST /api/v2/human-design/connection` Calculate Human Design connection chart - Two-person composite bodygraph compatibility
- `POST /api/v2/human-design/penta` Calculate Human Design Penta - Small-group BG5 operating system for three to five people

## Example request

```bash
curl -X POST "https://roxyapi.com/api/v2/human-design/connection" \
  -H "X-API-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"personA":{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"},"personB":{"date":"1990-07-15","time":"13:00:00","timezone":"America/New_York"}}'
```

## Example response

```json
{
  "totalChannels": 14,
  "channels": [
    {
      "gateA": 34,
      "gateB": 20,
      "name": "Charisma",
      "circuit": "Individual",
      "centers": [
        "throat",
        "sacral"
      ],
      "dynamic": "Electromagnetic",
      "personAGates": [
        34
      ],
      "personBGates": [
        20
      ]
    }
  ],
  "centers": [
    {
      "id": "sacral",
      "name": "Sacral",
      "defined": true,
      "definedBy": [
        "A"
      ]
    }
  ],
  "combinedDefinition": "Single",
  "summary": {
    "electromagnetic": 3,
    "dominance": 2,
    "compromise": 1,
    "companionship": 4
  }
}
```

## Remote MCP

Every endpoint is a callable tool on the Remote MCP server at https://roxyapi.com/mcp/human-design over Streamable HTTP. Tool name for `POST /human-design/connection`: `post_human_design_connection`. `tools/list` is free; `tools/call` bills the same as REST.

## FAQ

### What does the Human Design Compatibility API return?

Calculate a Human Design connection chart by overlaying two bodygraphs. Every response is structured JSON with documented fields, not free text, so you map it straight into your product.

### How do I authenticate with the Human Design Compatibility API?

Pass your key in the X-API-Key header on every request. Keys are delivered instantly at checkout with no approval queue. Use a secret sk key server side, or mint a publishable pk key locked to your origins for browser and no-code use.

### Does the Human Design Compatibility API support multiple languages?

Yes. Append the lang query parameter to any endpoint for responses in English, German, Spanish, French, Hindi, Portuguese, Russian and Turkish. The translated payload includes the full interpretation text, not just field labels.

### Do I need coordinates to call the Human Design Compatibility API?

No. Call GET /location/search with a city name first, then pass latitude, longitude, and timezone from the first result into the request. Never ask users to type coordinates. Timezone accepts a decimal offset or an IANA name.

### Is the Human Design Compatibility API available over Remote MCP for AI agents?

Yes. Every endpoint is exposed as a callable tool on the Remote MCP server at https://roxyapi.com/mcp/human-design over Streamable HTTP, so Claude, ChatGPT, Cursor, and any MCP client auto-discover it with no local setup or Docker.

### How is the Human Design Compatibility API billed?

Flat pricing: 1 request equals 1 quota unit, REST and MCP identical, with no credit weighting or per-token markup. Every plan includes all 12 domains, so the Human Design Compatibility API is included at no extra cost.

### What lang values does the Human Design Compatibility API accept?

The lang parameter accepts en, tr, de, es, hi, pt, fr, ru. Case-insensitive where it is a path value.

## Full reference

Fetch the OpenAPI spec at https://roxyapi.com/api/v2/human-design/openapi.json. Master agent manifest at https://roxyapi.com/llms.txt.