Agents
An agent belongs to a gateway and defines how one class of AI traffic is proxied: the upstream route, default model and model policy, budgets, streaming, and firewall / PII policies. Once created, an agent is served on the data plane at/v1/ai/{slug} — see Execute AI Request to send it traffic.
These endpoints are the public /v1 control-plane equivalent of the dashboard agent pages. See the control-plane overview for authentication, the response envelope, pagination, and error types.
/v1 never exposes KnoxCall-managed system agents (for example the Workflows system agent). Reads, updates, token operations, and deletes against a system agent return 404 not_found.The agent object
An agent is returned with its full configuration. The most commonly used fields:
The object also includes the remaining agent settings (
fallback_route_ids, model_rewrite, budget_overage_action, pii_detokenize_response, pii_streaming_holdback_chars, cache_mode, output_schema, output_validation_action, and others) at their configured or default values.
List agents
page, per_page). Requires the read capability. Returns 404 not_found if the gateway does not belong to your tenant.
{ data, meta }.
Create an agent
write capability.
Request body
{ data, meta }:
name or slug returns 400 validation; an invalid slug returns 422 invalid_slug; a duplicate slug returns 409 conflict.
Get an agent
read capability. Returns 404 not_found if the agent does not belong to your tenant or is a system agent.
Update an agent
write capability. The slug cannot be changed.
Updatable fields
name, description, primary_route_id, default_model, model_allowlist, model_denylist, budget_daily_usd, budget_monthly_usd, streaming_enabled, firewall_policy_id, pii_redact_policy_id, pii_detokenize_response, tool_allowlist.
Reference fields (primary_route_id, firewall_policy_id, pii_redact_policy_id) are tenant-ownership checked exactly as on create.
{ data, meta }.
Archive an agent
write capability.