Skip to main content
The Frontier Gateway API manages the resources behind your branded inference gateway: the endpoints that route slugs to deployments, the groups that model your customers and their limits, and the federated API keys your customers call with. For the conceptual guide and end-to-end examples, see the Frontier Gateway overview. These endpoints live under /v1/gateway/ and are gated to Frontier Gateway workspaces. Authenticate with a workspace API key with management scope, passed as Authorization: Api-Key $BASETEN_API_KEY. Requests from workspaces that aren’t onboarded return 403. The full OpenAPI spec is available at api.baseten.co/v1/spec for generating API clients.

​
Endpoints

An endpoint maps a routing slug to the deployment that serves it. Use these routes to create, inspect, re-point, and delete endpoints.

​
Groups

A group owns the model set, rate and usage limits, and place in the hierarchy that its keys inherit. Use these routes to manage groups and inspect their usage.

​
API keys

A federated API key is the credential your customers call with, bound to one group whose limits it inherits. Use these routes to mint, list, and revoke keys.

​
Billing webhooks

Frontier Gateway emits a signed per-request usage event to your webhook endpoint for every call. For the payload shape and signature verification, see Billing webhooks.