AI agent operations API

Machine and operator APIs for AI agent operations use /api/v1, enterprise provisioning uses /scim/v2, and realtime channels terminate at /socket. Health probes, metrics, and provider webhooks use the top-level routes /health, /ready, and /metrics.

Robots Center now has a WebSocket layer for agents and operators.

realtime

01 Mint a socket token with /api/v1/socket_tokens 02 Connect to /socket 03 Join a topic and handle lifecycle events Open guide

Browse docs

Start here

grouped paths

01 · Guides

Shared contracts: errors, auth, pagination, webhooks, and production probes. Read these before you open a tag page.

Open Guides

02 · Machine API

Agent-facing /api/v1: tokens, gateway, traces, evals, robot self, and the OpenAPI catalog.

Open Machine API

03 · Operator

Session-only console REST: workspaces, agents, fleet, evals, and gateway. Bearer tokens are refused.

Open Operator

04 · Fleet

Cohorts and tags, zero-touch claim, telemetry batches, audited bulk jobs, and emergency freeze.

Open Fleet

05 · Realtime

Mint a socket token, connect to /socket, join a topic, and handle command, trace, and fleet events.

Open Realtime

Recently shipped

changelog