Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.

<! generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten Overview Create, list, rotate, and revoke OmniRoute API keys. Control per key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints. Authentication All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE API KEY=false for local development. Endpoints GET /api/keys List API keys POST /api/keys Create API key GET /api/keys/{id} Get API key PATCH /api/keys/{id} Update API key DELETE /api/keys/{id} Delete API key POST /api/keys/{id}/access Add or remove allowed models and combos on an API key atomically Adds or removes allowed models and combos on an API key without lost updates. Serialized per key ID using an in process async lock. Keys allowing all models (modelAccessMode: all) or all combos (allowedCombos containing 'combo/ ') require switchToRestricted: true when adding new models or combos, otherwise returning a 409 Conflict. When switching to restricted mode, the allowlist becomes exactly the net added items (at least one required). Direct concurrent PATCH calls to /api/keys/{id} completely overwrite the policy outside this lock. GET /api/keys/{id}/devices List devices for an API key Lists the distinct devices (masked IP + User Agent fingerprints) tracked for an API key by the in memory device tracker. IPs are masked before storage; the route never sees the raw client IP. POST /api/keys/{id}/regenerate POST keys › <id › regenerate GET /api/keys/{id}/reveal GET keys › <id › reveal GET /api/keys/{id}/usage limits GET keys › <id › usage limits GET /api/keys/groups GET keys › groups POST /api/keys/groups POST keys › groups GET /api/keys/groups/{id} GET keys › groups › <id PUT /api/keys/groups/{id} PUT keys › groups › <id Updates the group. Setting isActive to false pauses its allow rules while preserving membership restrictions and deny rules. Other active groups may still grant access unless a deny matches. Keys belonging only to inactive groups have no group grants. Keys without groups remain unrestricted by group policy; per key restrictions still apply. DELETE /api/keys/groups/{id} DELETE keys › groups › <id GET /api/keys/groups/{id}/keys GET keys › groups › <id › keys POST /api/keys/groups/{id}/keys POST keys › groups › <id › keys DELETE /api/keys/groups/{id}/keys DELETE keys › groups › <id › keys GET /api/keys/groups/{id}/permissions GET keys › groups › <id › permissions POST /api/keys/groups/{id}/permissions POST keys › groups › <id › permissions DELETE /api/keys/groups/{id}/permissions DELETE keys › groups › <id › permissions Payloads See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

omni-api-keys