# Happyrobot

> HappyRobot is an AI orchestration platform for deploying AI agents ("AI workers") into operational
> enterprise workflows — logistics and freight brokerage first, plus utilities, airlines, finance,
> insurance, manufacturing, retail and telecom. Agents place and answer phone calls, send and receive
> email, SMS, WhatsApp and chat, read and write to TMS/ERP systems, and execute multi-step workflows built
> as node graphs. The Happyrobot Public API (v2) exposes 205 operations across 32 resource families, and
> two first-party remote MCP servers expose 35 tools for building, testing and governing those workflows.

Generated by the API Evangelist enrichment pipeline on 2026-08-01. Not published by Happyrobot.
Probed values carry their HTTP status in the repo artifacts.

## APIs

- [Happyrobot Public API (v2)](https://platform.happyrobot.ai/api/v2): 205 operations, 162 paths, OpenAPI 3.0.3, bearer API key
- [Happyrobot Platform API (v1, legacy)](https://platform.happyrobot.ai/api/v1): 10 read-only operations, OpenAPI 3.0.2, `authorization` + `x-organization-id` headers
- [EU cluster](https://platform.eu.happyrobot.ai/api/v2): data-residency mirror serving the same v2 contract

## Specs

- [Public API OpenAPI 3.0.3](https://platform.happyrobot.ai/api/v2/docs/json) — served publicly and anonymously from the API host
- [Platform v1 OpenAPI 3.0.2](https://platform.happyrobot.ai/api/v1/openapi.json)

## MCP servers

- [Workflows MCP](https://mcp.platform.happyrobot.ai/workflows/mcp) — 26 tools + 5 prompts, Streamable HTTP, OAuth scope `mcp:full`
- [Twin MCP](https://mcp.platform.happyrobot.ai/twin/mcp) — 9 tools over the customer's Twin SQL database, scope `mcp:full`
- [Workflows MCP, EU](https://mcp.platform.eu.happyrobot.ai/workflows/mcp)
- [Docs MCP](https://docs.happyrobot.ai/mcp) — documentation search, scope `mcp:search`
- Install: `claude mcp add --transport http happyrobot-workflows https://mcp.platform.happyrobot.ai/workflows/mcp`

## Discovery documents

- [security.txt](https://happyrobot.ai/.well-known/security.txt) — RFC 9116, Contact `security@happyrobot.ai`
- [OIDC configuration](https://auth.happyrobot.ai/.well-known/openid-configuration) — Auth0 tenant for console sign-in
- [OAuth authorization server (platform)](https://platform.happyrobot.ai/.well-known/oauth-authorization-server) — RFC 8414, scope `mcp:full`
- [OAuth protected resource (workflows MCP)](https://mcp.platform.happyrobot.ai/.well-known/oauth-protected-resource/workflows/mcp) — RFC 9728
- [OAuth authorization server (docs MCP)](https://docs.happyrobot.ai/.well-known/oauth-authorization-server) — scope `mcp:search`
- No A2A agent card is published on any host.

## SDKs

- [@happyrobot-ai/sdk](https://www.npmjs.com/package/@happyrobot-ai/sdk) — TypeScript, `npm install @happyrobot-ai/sdk`
- [happyrobot](https://pypi.org/project/happyrobot/) — Python, `pip install happyrobot`
- [@happyrobot-ai/workflow-sdk](https://www.npmjs.com/package/@happyrobot-ai/workflow-sdk) — typed workflow authoring
- [@happyrobotai/web-client](https://www.npmjs.com/package/@happyrobotai/web-client) — browser WebRTC client (UMD on jsDelivr)

## Docs

- [Documentation](https://docs.happyrobot.ai) — NOTE: the docs host is behind an access-code gate; anonymous clients receive "Access Restricted"
- [API reference](https://docs.happyrobot.ai/api-reference)
- [Getting started](https://docs.happyrobot.ai/getting_started)
- [Pricing](https://docs.happyrobot.ai/general/pricing)
- [Developer tools](https://www.happyrobot.ai/product/developer-tools)
- [Security and reliability](https://www.happyrobot.ai/product/security-and-reliability)

## Operations and trust

- [Status page](https://status.happyrobot.ai/) — Atlassian Statuspage; components Platform, Voice, Text, Broker, Authentication & Authorization, Integrations & Dependencies
- [Trust center](https://trust.happyrobot.ai/) — Vanta-hosted
- Compliance claimed: SOC 2 Type II, GDPR, HIPAA, EU AI Act, NIST CSF, DORA
- [Terms](https://www.happyrobot.ai/legal/terms-and-conditions) · [Privacy](https://www.happyrobot.ai/legal/privacy-policy)

## Repo artifacts

- openapi/happyrobot-public-api-openapi.json
- openapi/happyrobot-platform-v1-openapi.json
- authentication/happyrobot-authentication.yml
- scopes/happyrobot-scopes.yml
- conventions/happyrobot-conventions.yml
- errors/happyrobot-problem-types.yml
- asyncapi/happyrobot-events.yml
- data-model/happyrobot-data-model.yml
- mcp/happyrobot-mcp.yml
- mcp/happyrobot-tool-crosswalk.yml
- lifecycle/happyrobot-lifecycle.yml
- conformance/happyrobot-conformance.yml
- sandbox/happyrobot-sandbox.yml
- components/happyrobot-components.yml
- packages/happyrobot-packages.yml
- security/happyrobot-domain-security.yml
- security/happyrobot-vulnerability-disclosure.yml
- security/happyrobot-trust-center.yml
- well-known/happyrobot-well-known.yml
- agentic-access/happyrobot-agentic-access.yml
- skills/_index.yml

## Integration notes for agents

- Auth: `Authorization: Bearer <sk_live_… | sk_test_…>`. A key is bound to one organization AND one
  environment; verify with `GET /api-key/describe`.
- Pagination is inconsistent: most collections use `page` + `page_size`; contacts and audit remarks use
  `cursor` + `limit`.
- There is NO idempotency key anywhere in the API. Retrying a POST after a timeout can create a duplicate
  run, purchase a second phone number, or publish a duplicate signal. Build your own dedupe.
- Errors are `{ error, message, statusCode, details }` — not RFC 9457. Three envelope variants exist
  (409 returns `{ message }` only; 413 returns `{ error, statusCode }`).
- 429 is declared on only three operations and no `Retry-After` or `RateLimit-*` header is documented.
- Environments are production / staging / development, plus a per-version `test` target. Webhook trigger
  nodes expose one URL per environment via `GET /versions/{version_id}/nodes/{node_id}`.
- The MCP surface is builder-shaped: all 26 Workflows tools author, version, test and govern workflows.
  Conversation data — contacts, memories, sessions, messages, knowledge bases, billing — is REST-only
  (55 of 205 operations have no MCP tool).