Skip to main content

Gateways

A gateway is the top-level container for AI agents. It carries an optional daily/monthly USD budget that applies across its agents. These endpoints are the public /v1 control-plane equivalent of the dashboard gateway pages — see the control-plane overview for authentication, the response envelope, and error types. Base path: https://api.knoxcall.com/v1/ai-gateway/gateways

The gateway object

List gateways

Returns your tenant’s gateways, paginated (page, per_page). Requires the read capability on ai_gateway.
Response

Create a gateway

Requires the write capability on ai_gateway. Request body
Response — the created gateway wrapped in { data, meta }:
Missing name or slug returns 400 validation; an invalid slug returns 422 invalid_slug; a duplicate slug returns 409 conflict.

Get a gateway

Returns a single gateway. Requires the read capability. Returns 404 not_found if the gateway does not belong to your tenant.

Update a gateway

Partial update — all fields optional. Requires the write capability. The slug cannot be changed. Request body
The response is the updated gateway wrapped in { data, meta }.

Archive a gateway

Soft-deletes (archives) the gateway and returns its id and new status. Requires the write capability.
Response
Archiving a gateway does not change the status of its agents. The data plane gates each request on the agent’s status, so an agent that is still active keeps serving traffic. To stop traffic, archive the agents directly.