agt_) and can be referenced by name or ID.
Base URL
All agent endpoints are under:Deploy Agent
Deploy a new agent to Superserve.Tarball (.tar.gz) containing the agent code and dependencies
Agent name (must be unique within your account)
Command to start the agent (e.g.,
bun run index.ts)JSON-encoded configuration object from
superserve.yamlAgent ID (prefixed with
agt_)Agent name
Start command for the agent
Environment variable names available to the agent
Secret keys that must be set before the agent can run
Dependency installation status:
pending, installing, ready, or failedError message if dependency installation failed
ISO 8601 timestamp when the agent was created
ISO 8601 timestamp when the agent was last updated
List Agents
Retrieve all agents in your account.Maximum number of agents to return
Array of agent objects (same schema as deploy response)
Get Agent
Retrieve details for a specific agent.Agent ID (e.g.,
agt_abc123)Delete Agent
Delete an agent and all its sessions.Agent ID (e.g.,
agt_abc123)Deployment Status
Thedeps_status field indicates the current state of the agent’s dependency installation:
| Status | Description |
|---|---|
pending | Dependencies queued for installation |
installing | Dependencies currently being installed |
ready | Agent is ready to receive requests |
failed | Dependency installation failed (see deps_error) |
Error Responses
HTTP status code
Error message
Additional error context
| Status | Message | Hint |
|---|---|---|
| 401 | Not authenticated | Run superserve login to authenticate |
| 404 | Agent not found | Run superserve agents list to see your agents |
| 409 | Agent already exists | Use a different name or delete the existing agent |
| 422 | Invalid input | Check your request parameters |