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
page, per_page). Requires the read capability on ai_gateway.
Create a gateway
write capability on ai_gateway.
Request body
{ data, meta }:
name or slug returns 400 validation; an invalid slug returns 422 invalid_slug; a duplicate slug returns 409 conflict.
Get a gateway
read capability. Returns 404 not_found if the gateway does not belong to your tenant.
Update a gateway
write capability. The slug cannot be changed.
Request body
{ data, meta }.
Archive a gateway
write capability.
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.