Skip to main content
A consumer is the runtime identity of a calling application. It is what holds credentials and routing configuration, and its slug (a short, URL-safe random string) is the first path segment on the proxy:
Each consumer belongs to one gateway and has a type:

​
Routing modes

A consumer routes in one of two modes:

​
Inline routing

Inline consumers own their routing directly:

​
Model policies

model_policies maps a registry to { allowed: string[], default: string }. allowed restricts which models a consumer may request from that registry (empty = all); default is used when the request names no model and must be in allowed.

​
Credentials, headers, and MCP

​
Managing consumers

CRUD lives under /v1/gateways/{gateway_id}/consumers, plus attach/detach sub-resources:
  • …/{id}/registries/{registry_id} — attach a registry (body { "weight": 1..100 }).
  • …/{id}/roles/{role_id} — attach a role (role-based mode).
  • …/{id}/auths/{auth_id} — attach an auth credential.
  • …/{id}/policies/{policy_id} — attach a policy.
See the Consumers API.