API Reference

RESTful APIs for HUMΛN Protocol integration. Protected routes require authentication.

REST APIBearer tokenJSONv1RFC 7807

API status

Operational

Base URL

https://api.haio.run

OpenAPI

3.0.x (see /ai/openapi.json)

Response format

application/json · list endpoints use cursor pagination

These APIs enable you to build AI systems that are accountable, trustworthy, and human-centric.

Every endpoint creates an immutable provenance record. Every action requires proper delegation. Every decision can be audited. This is how AI earns trust.

Base URL

https://api.haio.run

Versioned resources use paths such as /v1/... (see OpenAPI).

Authentication

Authenticated requests use a valid API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Obtain keys from your organization or environment setup. For delegation-heavy flows, you may also use delegation tokens from POST /v1/delegation-tokens per the OpenAPI spec.

Use with AI

Connect your coding assistant to the HUMΛN API: download compact context for any LLM, or wire the official MCP server so Cursor and Claude Desktop can call curated API tools with your key.

LLM context file

A concise, LLM-oriented summary of auth, concepts, and links. Paste into any model, or point tools at the hosted URL.

Download llms.txt OpenAPI spec (JSON)

/ai/llms.txt

Cursor MCP

Add to ~/.cursor/mcp.json or .cursor/mcp.json in your project. Replace YOUR_API_KEY.

.cursor/mcp.json

{
  "mcpServers": {
    "human": {
      "command": "npx",
      "args": ["-y", "@human/mcp"],
      "env": {
        "HUMAN_API_KEY": "YOUR_API_KEY",
        "HUMAN_API_URL": "https://api.haio.run"
      }
    }
  }
}

Claude Desktop MCP

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Requires Node.js 18+ for npx.

claude_desktop_config.json

{
  "mcpServers": {
    "human": {
      "command": "npx",
      "args": ["-y", "@human/mcp"],
      "env": {
        "HUMAN_API_KEY": "YOUR_API_KEY",
        "HUMAN_API_URL": "https://api.haio.run"
      }
    }
  }
}

Response format

Successful responses are JSON. Many list endpoints return data, has_more, and next_cursor for pagination.

Errors use RFC 7807 problem details (application/problem+json) with type, title, status, and detail; validation responses may include an errors array.

{
  "type": "https://haio.run/errors/validation",
  "title": "Validation failed",
  "status": 400,
  "detail": "One or more fields are invalid.",
  "errors": [ { "field": "cursor", "code": "INVALID_CURSOR", "message": "..." } ]
}

Rate limits

• Default: Per-route limits apply (see X-RateLimit-* headers on responses).
• Enterprise: Custom limits and quotas.