Skip to main content
GET
Get an AI gateway
Returns one gateway owned by your tenant. A gateway belonging to another tenant returns 404 not_found, so a probe cannot distinguish “not yours” from “does not exist”. A malformed id is 400 invalid_id. To list its agents, use List agents; its MCP servers, List MCP servers; its tokens — including agentless ones — List gateway tokens.
The dashboard twin. The same operation exists on the admin host as GET /admin/ai-gateway/{gatewayId}, session-authenticated with an X-Tenant-ID header and an owner/admin role. That is what the dashboard itself calls. Prefer the /v1 operation above for anything you write: it is the surface the five SDKs, the Postman collection and this spec cover.

Authorizations

Authorization
string
header
required

OAuth 2.1 authentication — recommended for new integrations. Access tokens (kc_ prefix) are minted at the root-host token endpoint https://api.knoxcall.com/oauth/token and passed as Authorization: Bearer <access_token>. Public clients must use PKCE with the authorization_code grant; confidential clients may use client_credentials. The first-party SDKs and the knoxcall login CLI handle token minting, caching, refresh, and DPoP for you.

Path Parameters

id
string<uuid>
required

The AI gateway UUID.

Response

The gateway.

data
object

An AI gateway — the top-level container that agents are created under.

meta
object

Metadata included with every API response.