Errors

Error shape

{
  "detail": "Human-readable message",
  "code": "AGENT_CONFIG_ERROR",
  "context": { "agent_id": "writer" }
}

detail is always present. code and context appear for domain-specific errors where a machine-readable discriminator matters (evaluator resolution failures, workflow step errors) — a generic validation error just uses FastAPI/Pydantic’s standard detail array shape.

Status codes

Code	Meaning
`400`	Malformed request body or query parameters
`401`	Missing, expired, or invalid bearer token
`403`	Authenticated, but not authorized for this resource (wrong tenant, missing RBAC scope)
`404`	Resource doesn’t exist — or exists in a tenant you can’t see, which looks identical from the outside (RLS never leaks existence)
`409`	Conflict — e.g. a tenant slug or domain that already exists
`422`	Request body fails schema validation
`429`	Rate limited — see Rate Limits
`500`	Unexpected server error — logged with a trace ID; not a signal to retry blindly

A 404 on a resource that belongs to a different tenant is indistinguishable from a 404 on a resource that doesn’t exist at all — this is deliberate. Row-Level Security means the query never sees the other tenant’s row to begin with, so there’s no information to leak.

Domain-specific codes

Code	Where it appears	Meaning
`AGENT_CONFIG_ERROR`	Agent/workflow runs	A manifest’s `entrypoint` or `evaluator` dotted path failed to resolve — a config error, never a silent skip
`DEDUPLICATED`	Agent runs	ADR-006 idempotency layer caught a duplicate execution attempt
`TOOL_LOOP_LIMIT`	Agent runs with tool calls	The bounded tool-call loop (10 iterations) exhausted without a final answer

API Reference

API Endpoints

Error shape

Status codes

Domain-specific codes

Rate Limits

​Error shape

​Status codes

​Domain-specific codes

Rate Limits

Error shape

Status codes

Domain-specific codes