Happyrobot

aid: happyrobot
name: Happyrobot
description: HappyRobot is an AI orchestration platform — "the AI operating system for the real economy" — that lets enterprises
  build, govern and deploy AI agents ("AI workers") into operational workflows across logistics, freight brokerage, 3PL, 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 in a visual
  builder. The Happyrobot Public API (v2) exposes 205 operations across 32 resource families — workflows, versions and nodes,
  runs, sessions and messages, contacts and memories, knowledge bases, phone numbers and SIP trunks, integrations, chat and
  voice tokens, signals, billing, plus a full agent-governance surface (audits, northstars, custom evals, adversarial tests
  and suites). Authentication is a bearer API key scoped to an organization and an environment; the platform additionally
  runs an Auth0 OIDC tenant for human sign-in and an OAuth 2.0 authorization server for its MCP surface.
url: https://raw.githubusercontent.com/api-evangelist/happyrobot/refs/heads/main/apis.yml
image: https://happyrobot.b-cdn.net/HappyRobot_HeroLoop_v01%20(00184)%201-1200x630.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.21'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- ai-agents
- agent-orchestration
- voice-ai
- conversational-ai
- logistics
- freight
- supply-chain
- workflow-automation
- contact-center
- telephony
- mcp
- agent-native
- agent-governance
- enterprise-automation
apis:
- name: Happyrobot Public API
  description: The current Happyrobot Public API (v2) — 205 operations over 162 paths, described by a live OpenAPI 3.0.3 document
    served from the API host at /api/v2/docs/json. Covers workflows, workflow folders and variables, versions and nodes, runs,
    sessions and messages, contacts and contact memories, knowledge bases, phone numbers, SIP trunks, toll-free verification,
    integrations (Slack, Teams, WhatsApp, Google Sheets, Twilio SMS, Telnyx SMS), chat and voice session tokens, realtime
    tokens, signals and scheduled signals, the Twin data store, billing usage, organization and members, MCP server registration,
    and the agent-quality surface (audits, issues, northstars, custom evals, adversarial tests and suites). Bearer API key
    auth, applied to every operation.
  humanURL: https://docs.happyrobot.ai/api-reference
  baseURL: https://platform.happyrobot.ai/api/v2
  tags:
  - ai-agents
  - agent-orchestration
  - workflow-automation
  - voice-ai
  - conversational-ai
  - telephony
  - agent-governance
  properties:
  - type: OpenAPI
    url: openapi/happyrobot-public-api-openapi.json
  - type: Documentation
    url: https://docs.happyrobot.ai/api-reference
  - type: APIReference
    url: https://docs.happyrobot.ai/api-reference
  - type: Authentication
    url: authentication/happyrobot-authentication.yml
  - type: Conventions
    url: conventions/happyrobot-conventions.yml
  - type: ErrorCatalog
    url: errors/happyrobot-problem-types.yml
  - type: DataModel
    url: data-model/happyrobot-data-model.yml
  - type: Overlay
    url: overlays/happyrobot-public-api-overlay.yaml
  - type: Webhooks
    url: asyncapi/happyrobot-events.yml
  - type: AgenticAccess
    url: agentic-access/happyrobot-agentic-access.yml
- name: Happyrobot Platform API v1
  description: The legacy v1 read API, described by an OpenAPI 3.0.2 document at /api/v1/openapi.json. Ten read-only operations
    covering runs, run recordings, use cases, workflow versions, issues and organization usage. Authenticated with an `authorization`
    header plus an `x-organization-id` header. One operation (GET /use-cases/{use_case_id}/runs) is explicitly marked DEPRECATED
    in favour of the v2 /runs endpoint.
  humanURL: https://docs.happyrobot.ai/api-reference
  baseURL: https://platform.happyrobot.ai/api/v1
  tags:
  - ai-agents
  - workflow-automation
  - telephony
  properties:
  - type: OpenAPI
    url: openapi/happyrobot-platform-v1-openapi.json
  - type: Documentation
    url: https://docs.happyrobot.ai/api-reference
  - type: Lifecycle
    url: lifecycle/happyrobot-lifecycle.yml
- name: Happyrobot Public API (EU cluster)
  description: EU data-residency mirror of the Happyrobot Public API, serving an identical OpenAPI 3.0.3 document with its
    own OAuth authorization server and its own MCP hosts. Selected in the SDKs and MCP packages with HAPPYROBOT_CLUSTER=eu.
    Verified live on 2026-08-01.
  humanURL: https://docs.happyrobot.ai/api-reference
  baseURL: https://platform.eu.happyrobot.ai/api/v2
  tags:
  - ai-agents
  - workflow-automation
  - data-residency
  properties:
  - type: OpenAPI
    url: openapi/happyrobot-public-api-openapi.json
  - type: Documentation
    url: https://docs.happyrobot.ai/api-reference
- name: Happyrobot Workflows MCP Server
  description: 'Happyrobot''s first-party remote MCP server for building and governing workflows — 26 published tools plus
    5 MCP prompts, served over Streamable HTTP and protected by OAuth 2.0 (scope mcp:full, RFC 9728 protected-resource metadata,
    RFC 7591 dynamic client registration, PKCE S256). It supersedes the now deprecated stdio package @happyrobot-ai/mcp. The
    tool surface is builder-shaped: it covers workflow authoring, versioning, testing, evaluation and red-teaming, telephony
    and integrations, and binds to 150 of the 205 Public API operations. Live tools/list is auth-gated; the published tool
    list is captured verbatim from the vendor''s own package documentation.'
  humanURL: https://docs.happyrobot.ai/developer-tools/mcp
  baseURL: https://mcp.platform.happyrobot.ai/workflows/mcp
  tags:
  - mcp
  - agent-native
  - ai-agents
  - workflow-automation
  properties:
  - type: MCPServer
    url: mcp/happyrobot-mcp.yml
  - type: ToolCrosswalk
    url: mcp/happyrobot-tool-crosswalk.yml
  - type: MCP
    url: https://mcp.platform.happyrobot.ai/workflows/mcp
  - type: OAuthScopes
    url: scopes/happyrobot-scopes.yml
  - type: Documentation
    url: https://docs.happyrobot.ai/developer-tools/mcp
- name: Happyrobot Twin MCP Server
  description: First-party remote MCP server over the customer's Twin database — 9 published tools covering schema introspection,
    paginated reads, table creation, row insert/update/delete, table drop, and arbitrary SQL execution (SELECT, INSERT, UPDATE,
    DELETE and DDL). Streamable HTTP, OAuth 2.0 under the same single coarse mcp:full scope as the Workflows server, so there
    is no read-only scope with which to bind a research agent. Supersedes the deprecated stdio package @happyrobot-ai/mcp-twin.
  humanURL: https://docs.happyrobot.ai/developer-tools/mcp-twin
  baseURL: https://mcp.platform.happyrobot.ai/twin/mcp
  tags:
  - mcp
  - agent-native
  - database
  properties:
  - type: MCPServer
    url: mcp/happyrobot-mcp.yml
  - type: ToolCrosswalk
    url: mcp/happyrobot-tool-crosswalk.yml
  - type: MCP
    url: https://mcp.platform.happyrobot.ai/twin/mcp
  - type: OAuthScopes
    url: scopes/happyrobot-scopes.yml
- name: Happyrobot Docs MCP Server
  description: A hosted documentation-search MCP server on the docs host, discovered via RFC 9728 protected-resource metadata
    at https://docs.happyrobot.ai/.well-known/oauth-protected-resource. It advertises a single mcp:search scope through its
    own authorization server at https://docs.happyrobot.ai/mcp/oauth. The endpoint answers MCP JSON-RPC with HTTP 401 invalid_token
    plus a WWW-Authenticate Bearer challenge that points back at the protected-resource document, so its tool list requires
    an authenticated introspection.
  humanURL: https://docs.happyrobot.ai
  baseURL: https://docs.happyrobot.ai/mcp
  tags:
  - mcp
  - agent-native
  - documentation
  properties:
  - type: MCPServer
    url: mcp/happyrobot-mcp.yml
  - type: OAuthScopes
    url: scopes/happyrobot-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.happyrobot.ai/
- type: DeveloperPortal
  url: https://docs.happyrobot.ai
- type: Documentation
  url: https://docs.happyrobot.ai
- type: APIReference
  url: https://docs.happyrobot.ai/api-reference
- type: GettingStarted
  url: https://docs.happyrobot.ai/getting_started
- type: Pricing
  url: https://docs.happyrobot.ai/general/pricing
- type: SignUp
  url: https://app.happyrobot.ai/signup
- type: Login
  url: https://app.happyrobot.ai/login
- type: Blog
  url: https://www.happyrobot.ai/blog
- type: TermsOfService
  url: https://www.happyrobot.ai/legal/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.happyrobot.ai/legal/privacy-policy
- type: Support
  url: https://www.happyrobot.ai/contact
- type: GitHubOrganization
  url: https://github.com/happyrobot-ai
- type: StatusPage
  url: https://status.happyrobot.ai/
- type: TrustCenter
  url: https://trust.happyrobot.ai/
- type: Compliance
  url: https://www.happyrobot.ai/product/security-and-reliability
- type: Security
  url: https://happyrobot.ai/.well-known/security.txt
- type: Packages
  url: packages/happyrobot-packages.yml
- type: SDKs
  url: packages/happyrobot-packages.yml
- type: WellKnown
  url: well-known/happyrobot-well-known.yml
- type: SecurityTxt
  url: well-known/happyrobot-security.txt
- type: OpenIDConnect
  url: well-known/happyrobot-openid-configuration.json
- type: Authentication
  url: authentication/happyrobot-authentication.yml
- type: OAuthScopes
  url: scopes/happyrobot-scopes.yml
- type: Conventions
  url: conventions/happyrobot-conventions.yml
- type: ErrorCatalog
  url: errors/happyrobot-problem-types.yml
- type: Lifecycle
  url: lifecycle/happyrobot-lifecycle.yml
- type: Conformance
  url: conformance/happyrobot-conformance.yml
- type: DomainSecurity
  url: security/happyrobot-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/happyrobot-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/happyrobot-trust-center.yml
- type: Sandbox
  url: sandbox/happyrobot-sandbox.yml
- type: DataModel
  url: data-model/happyrobot-data-model.yml
- type: Webhooks
  url: asyncapi/happyrobot-events.yml
- type: MCPServer
  url: mcp/happyrobot-mcp.yml
- type: ToolCrosswalk
  url: mcp/happyrobot-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/happyrobot-agentic-access.yml
- type: LLMsTxt
  url: llms/happyrobot-llms.txt
- type: Components
  url: components/happyrobot-components.yml
- type: Overlay
  url: overlays/happyrobot-public-api-overlay.yaml
- type: MCP
  url: https://mcp.platform.happyrobot.ai/workflows/mcp
x-enrichment-notes:
  documentation_access: docs.happyrobot.ai is behind an access-code gate — every path returns "Access Restricted" to anonymous
    clients. The Documentation, APIReference, GettingStarted and Pricing pointers above are Happyrobot's real, published documentation
    URLs (several are search-engine indexed), but they are NOT anonymously readable as of 2026-08-01. Recorded so the gap
    is visible rather than silently scored as open docs.
  idempotency: Deliberately NOT wired. The string "idempot" does not appear anywhere in either OpenAPI document, so no Idempotency
    pointer is emitted. See conventions/happyrobot-conventions.yml.
  agent_card: Deliberately NOT wired. /.well-known/agent-card.json and /.well-known/agent.json were probed on happyrobot.ai,
    www, platform, app, docs and mcp.platform — all 404, 302, 429, or an HTML SPA shell. No agent card is published, so no
    a2a/ artifact was authored.
  changelog: No ChangeLog pointer. No dated changelog is publicly readable — the docs changelog is behind the access gate
    and the marketing site has no changelog page or RSS feed.
  cli: No CLI artifact. The two npm binaries (happyrobot-mcp, happyrobot-mcp-twin) are MCP server entry points, now deprecated,
    not a general-purpose command-line interface.
  deprecation: No Deprecation pointer. Real deprecations exist and are recorded in lifecycle/ (the v1 /use-cases/{use_case_id}/runs
    operation, and both stdio MCP npm packages), but Happyrobot publishes no deprecation POLICY page and supports neither
    the RFC 8594 Sunset header nor a Deprecation header, and no operation in either OpenAPI carries deprecated:true. Emitting
    the pointer would over-claim.
  contract_discovery: The v2 OpenAPI was NOT at any conventional docs-host path — docs.happyrobot.ai answers 200 with an identical
    application shell for /openapi.json, /llms.txt, /docs.json and every other path. The real 687KB OpenAPI 3.0.3 is served
    anonymously from the API host at https://platform.happyrobot.ai/api/v2/docs/json (a Fastify swagger route; /api/v2/openapi.json
    404s). Recorded so a future pass does not repeat the search.
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 34
  pass: local-v1