Log in Create workspace
Skip to content

Choosing a workflow? Explore the operations solutions before opening the API reference.

Developer resources

AI agent operations API

Connect your agents and robots, understand their work, and control which actions they can take. Start with a credential and one small request, then follow the guide for your workflow.

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, /metrics, and /webhooks/nowpayments.

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

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

New to Robots Center?

From a workspace to your first request

A workspace contains your team, agents, and operational data. A service agent is the software identity making API requests. Its credential decides which workspace it can access and which actions it can perform.

  1. Choose the right identity

    Use a scoped API credential for software or robots. Use your signed-in browser session for the operator API. These credentials are not interchangeable.

  2. Get a credential and make a small request

    Follow the Authentication quickstart to obtain a key, send it securely, and check the response before adding writes to your integration. Already have a key? You do not need to register again.

  3. Follow one workflow from start to finish

    Record an execution trace, authorize a tool call, or connect a robot. Each topic explains setup, examples, expected results, and what to do if a request fails.

A useful first milestone

Your request returns the expected data from the intended workspace. If it does not, start with the error response guide rather than retrying a write blindly.

Start here

grouped paths

Recently shipped

changelog