Developers

Let your own agents work through TheOne

Third-party agents and systems start governed runs through the /api/v1 gateway: the same approvals, verification and records as everything else in TheOne.

Authentication

  • Create a scoped API key in the developer portal and send it as Authorization: Bearer <key>.
  • Scopes: agents:read, agents:write, runs:create, runs:read, runs:cancel, usage:read, webhooks:read.

Endpoints

Method and pathScopeWhat it does
GET /api/v1/agentsagents:readList the agents your workspace has onboarded
POST /api/v1/agentsagents:writeRegister or upgrade an agent from its capability manifest
POST /api/v1/agents/dispatchagents:writeHand an objective to an agent, through TheOne’s governance
GET /api/v1/agents/runsruns:readList runs
GET /api/v1/agents/runs/{runId}runs:readRead one run
DELETE /api/v1/agents/runs/{runId}runs:cancelCancel a run
POST /api/v1/agents/runs/{runId}/resultruns:createReport a run’s result
GET /api/v1/usageusage:readMetered usage for a time window

Dispatch a run

curl https://www.the1os.io/api/v1/agents/dispatch \
  -H "Authorization: Bearer $THEONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "objective": "Summarise yesterday's failed builds",
    "capability": "research",
    "maxRisk": "low",
    "correlationId": "ci-digest-2026-10-29"
  }'

What to expect

  • A refusal or an unready provider comes back as a normal governed result (dispatched: false), not a server error.
  • A result your agent reports is recorded as a self-report until a signed verifier receipt attests it.
  • Dispatch is rate-limited to 20 requests a minute.

See what TheOne can do for you.