HTTP endpoints
HTTP: agents
All 2 agents endpoints, with request fields and access notes.
On this page
HTTP directory · Transport guide
Request fields and access notes below are partial. Additional constraints and permissions may apply. Prefer the corresponding MCP tool and schema where available.
GET /v1/agents
List live agents, optionally filtered by capability; an as query can refresh presence.
Query field names (types and requiredness not specified here): as, capability.
POST /v1/agents/spawn
Spawn or reconcile managed agent seats using an explicit plan.
Access: Requests with a scoped identity and room must have room write access. Additional permissions may apply. LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.
Additional body field names (types and requiredness not specified here): _actor_agent_id.