Skip to main content
An endpoint is the routing slug your customers call, like my-org/glm-5.2, plus the target it points to. When a request reaches the gateway with that slug, the gateway routes it to the target. You manage endpoints yourself through the REST API, so you can stand up a new slug, re-point it at a different deployment, or retire it.
To enable Frontier Gateway for your workspace, talk to us.

​
Concepts

An endpoint has two parts:
  • Slug: a globally-unique routing identifier of the form {org_prefix}/{name}, such as my-org/glm-5.2, where the prefix is one your organization owns. You can rename a slug as long as the new value is globally unique and keeps a prefix your organization owns.
  • Target: where the slug routes. A target is either a Baseten deployment (provider: BASETEN, with the model_id it should serve) or an external model provider such as Anthropic (provider: ANTHROPIC) or OpenAI (provider: OPENAI). An endpoint takes a list of targets but holds exactly one today.

​
Endpoints and groups

Endpoints and groups answer two different questions:
  • An endpoint defines what a slug routes to: which deployment serves traffic for my-org/glm-5.2.
  • A group defines who can call a slug and how much: the model slugs a federated key may call, plus its rate and usage limits.
To serve a model to a customer, create an endpoint for the slug, then grant a group access to that same slug and mint the customer a key under it. The slug ties the two together.

​
Create an endpoint

Create an endpoint to give your customers a stable slug to call that routes to one of your deployments. The request body takes the slug and a targets list with one Baseten target. The response is the new endpoint; save the id, which is the path parameter for every per-endpoint operation that follows. 
curl --request POST \
  --url https://api.baseten.co/v1/gateway/endpoints \
  --header "Authorization: Api-Key $BASETEN_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "slug": "my-org/glm-5.2",
    "targets": [
      {
        "provider": "BASETEN",
        "model_id": "3kZ9xqd"
      }
    ]
  }'
For more information, see POST /v1/gateway/endpoints.

​
List endpoints

List your endpoints to see every slug you’ve published and where each one routes. The response is paginated: pass limit and cursor query parameters to page through results, and follow pagination.cursor while pagination.has_more is true. 
curl --request GET \
  --url https://api.baseten.co/v1/gateway/endpoints \
  --header "Authorization: Api-Key $BASETEN_API_KEY"
For more information, see GET /v1/gateway/endpoints.

​
Get an endpoint

Get an endpoint by its id to check where a single slug currently routes, for example to confirm a change took effect. 
curl --request GET \
  --url https://api.baseten.co/v1/gateway/endpoints/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"
For more information, see GET /v1/gateway/endpoints/{endpoint_id}.

​
Re-point an endpoint

Re-point an endpoint to move a live slug to a different deployment, like promoting a new model version, without asking your customers to change the name they call. The slug stays the same; you replace the endpoint’s full target list. The gateway syncs endpoints every 60 seconds, so a change can take up to a minute to take effect. 
curl --request PATCH \
  --url https://api.baseten.co/v1/gateway/endpoints/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "targets": [
      {
        "provider": "BASETEN",
        "model_id": "7mP2wqe"
      }
    ]
  }'
For more information, see PATCH /v1/gateway/endpoints/{endpoint_id}.

​
Delete an endpoint

Delete an endpoint to take a slug out of service, whether you’re retiring a model or freeing the slug for reuse. The gateway stops routing the slug. 
curl --request DELETE \
  --url https://api.baseten.co/v1/gateway/endpoints/abc123hash \
  --header "Authorization: Api-Key $BASETEN_API_KEY"
For more information, see DELETE /v1/gateway/endpoints/{endpoint_id}.

​
Next steps