API introduction - CelerFlow

Base URL

https://api.celerflow.ai/functions/v1/

CelerFlow uses consolidated Edge Functions with sub-routes. Each function handles multiple related operations:

Function	Routes
`/agent`	Register, health, terminate, disconnect, remove, policies, confirmations
`/fleet`	Create, list, get, delete
`/trace`	Ingest spans (batch)
`/notify`	Notification delivery (Telegram, Slack, WhatsApp)
`/cli`	Device code, device token
`/team`	Create, invite, list members, remove member
`/audit`	Create export, list exports, download
`/stripe`	Webhook handler
`/api-key`	Create, list, revoke
`/risk`	Query risk alerts, resolve alerts
`/mcp`	MCP Gateway proxy (coming soon)

Most endpoints require a Bearer token:

Authorization: Bearer YOUR_TOKEN

Four authentication methods:

User token (JWT) — from the device code OAuth flow. Used for dashboard and workspace operations.
Bootstrap token — assigned to an agent on connection (bt_xxx). Used for health reporting, trace ingestion, and agent-specific operations.
API key — created from Settings → API Keys (cf_xxx). Used for programmatic access and the MCP Gateway.
Device code — temporary code used during the celerflow login CLI flow.

Success:

{
  "id": "fleet_abc123",
  "name": "Production",
  "created_at": "2026-01-15T10:30:00Z"
}

Error:

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Fleet not found",
    "status": 404
  }
}

Resource	Free	Pro	Team	Enterprise
Agents	3	20	100	Unlimited
Workspaces	1	5	20	Unlimited
Team members	1	1	10	Unlimited
Traces/day	1,000	50,000	200,000	Unlimited
Trace retention	3 days	30 days	90 days	365 days

Rate-limited requests return HTTP 429 with a Retry-After header.