Skip to content
Development
Skill

/omni-api-keys

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.

From plugin
omniroute
86k46 skills

Claude Code

$ npx -y skills add cheaper-inference/omniroute --skill omni-api-keys --agent claude-code

SKILL.md

omni-api-keys.SKILL.md
name: omni-api-keys
description: 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

curl http://localhost:20128/api/keys \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/keys

Create API key

Submit the legacy key settings, or name with a complete policy and optional templateRef containing id and revision. Policy-based creation writes the key and related settings atomically. Submitted edits are final; templateRef is provenance and never replaces the policy. The fresh secret is returned once with Cache-Control no-store. Blocking missing references return 422.

curl -X POST http://localhost:20128/api/keys \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/keys/{id}/template-policy

Preview a key policy without revealing its credential

curl http://localhost:20128/api/keys/{id}/template-policy \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/keys/import

Import a caller-supplied API key without replacing existing keys

Uses the same management authentication as POST /api/keys: dashboard session, local CLI credential, manage/admin-scoped API key, or an admin oma_ access token. read/write oma_ tokens are insufficient. When login is disabled, inference-only imports may be anonymous, but importing manage/admin scopes requires a real management credential, including retries against an existing management-scoped key.

Accepts a 32–256 character ASCII key beginning with sk-, followed only by A–Z, a–z, 0–9, underscore or hyphen. No machine-id or CRC validation is performed. Whitespace is rejected, never trimmed. Configured environment API keys and the internal self-loop credential cannot be imported because they bypass row policy.

An explicit existing id with the same key hash returns 200 and the existing stored policy without mutation; requested name/policy changes are ignored. An existing id with a different value, or the same value at another id, returns 409 without disclosing another id. Without id, a UUID is generated and duplicate values return 409, not 200. New imports return 201. No rekey is performed.

Identity checks and the complete policy insert run in one synchronous SQLite IMMEDIATE transaction. Uses create-key defaults and scope normalization (adds self:usage and removes duplicates). Unknown fields, including isActive, are ignored just as on create; change active state through the existing PATCH route. No settings, providers, combos or session state is imported. This does not change the operator-only import-json restore permissions. Cloud sync is best-effort and asynchronous for new imports only. Secrets use enc:v1 encryption at rest when storage encryption is configured; otherwise upstream plaintext storage applies. Responses contain only id/name, a masked key and whitelisted stored policy fields, never the full secret, hash, key prefix column or machine identifier.

: "${IMPORTED_API_KEY:?Set the caller-supplied sk- key to import}"
curl -X POST http://localhost:20128/api/keys/import \
  -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Content-Type: application/json" \
  -d "{\"name\":\"Imported key\",\"key\":\"$IMPORTED_API_KEY\"}"

GET /api/keys/{id}

Get API key

curl http://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PATCH /api/keys/{id}

Update API key

curl -X PATCH http://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/keys/{id}

Delete API key

curl -X DELETE http://localhost:20128/api/keys/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

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.

curl -X POST http://localhost:20128/api/keys/{id}/access \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

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.

curl http://localhost:20128/api/keys/{id}/devices \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/keys/{id}/regenerate

POST keys › <id> › regenerate

curl -X POST http://localhost:20128/api/keys/{id}/regenerate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/keys/{id}/reveal

GET keys › <id> › reveal

curl http://localhost:20128/api/keys/{id}/reveal \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/keys/{id}/usage-limits

GET keys › <id

Read more
@diegosouzapw
Ships withomniroute

Created by Diego Souza

Stars on GitHub

Momentum

stars in total
86.1k
Star history of diegosouzapw/OmniRoute on GitHub, a chart by star-history.com

Other skills on omniroute.

cli-a2a

cli-a2a

Interact with the OmniRoute A2A server from the CLI. Send tasks, inspect skill execution history, and test the JSON-RPC 2.0…

cli-backup-sync

cli-backup-sync

Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules,…

cli-batches

cli-batches

Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and…

cli-chat

cli-chat

Send chat completions, stream responses, and start an interactive REPL session from the CLI. Supports all OmniRoute providers,…

cli-compression

cli-compression

Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview…

cli-contexts

cli-contexts

Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills12d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react3d252k
@facebook@facebookInstall Skill

Questions about omni-api-keys.

Which coding agents can use omni-api-keys?
omni-api-keys installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.