Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Omni Providers · diegosouzapw | DecimalAI

diegosouzapw/omni-providers

SkillScore96Maintained

Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations (OpenAI, Anthropic, Gemini, and 160+).

agent-toolingby diegosouzapw

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

AI Engineer pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/diegosouzapw-omni-providers/SKILL.md

decimalai skills pull diegosouzapw-omni-providers --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/diegosouzapw-omni-providers/SKILL.md https://app.decimal.ai/s/diegosouzapw-omni-providers/SKILL.md

Raw file: /s/diegosouzapw-omni-providers/SKILL.md ↗ · machine-readable summary at /s/diegosouzapw-omni-providers.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

Runs

all versions · 30d

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

25 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 18d ago

Yes — +80% lift · at higher cost+333% tokens0% turns96% of whole cases pass with skill (24/25)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-09	✗→✓	▲ Improved	176%	0%
case-01	✗→✓	▲ Improved	331%	0%
case-02	✗→✓	▲ Improved	309%	0%
case-03	✗→✓	▲ Improved	361%	0%
case-04	✗→✓	▲ Improved	326%	0%

Showing 5 of 25 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/8/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

diegosouzapw / omniroute

skills/omni-providers/SKILL.md

View on GitHub ↗

License MITImported 9/8/2026Version v4

Skill contents

SKILL.md

Overview

Manage provider connections, API keys, OAuth flows, and connection tests via the REST API. List, add, update, remove, and test AI provider integrations across OmniRoute's 327-provider catalog.

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/providers

List provider connections

bash
curl https://localhost:20128/api/providers \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers

Create provider connection

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

GET /api/providers/{id}

Get provider connection

bash
curl https://localhost:20128/api/providers/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PATCH /api/providers/{id}

Update provider connection

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

DELETE /api/providers/{id}

Delete provider connection

bash
curl -X DELETE https://localhost:20128/api/providers/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/{id}/test

Test provider connection

bash
curl -X POST https://localhost:20128/api/providers/{id}/test \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/{id}/models

List models for a provider

bash
curl https://localhost:20128/api/providers/{id}/models \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/providers/cursor/agent-availability

Check cursor-agent availability

Credential-free, informational check for whether cursor-agent is installed and authenticated on this host — backs the dashboard's dismissible install-nudge banner. Returns only cursorAgentAvailable (boolean); never tokens or machineId.

bash
curl https://localhost:20128/api/providers/cursor/agent-availability \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/test-batch

Test multiple providers at once

bash
curl -X POST https://localhost:20128/api/providers/test-batch \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/validate

Validate provider credentials

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

GET /api/providers/client

Get client-side provider info

bash
curl https://localhost:20128/api/providers/client \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/agy-auth/import

Import an Antigravity CLI (agy) token file as an agy connection

bash
curl -X POST https://localhost:20128/api/providers/agy-auth/import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/agy-auth/import-bulk

Bulk-import multiple Antigravity CLI (agy) token files (up to 50)

bash
curl -X POST https://localhost:20128/api/providers/agy-auth/import-bulk \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/agy-auth/zip-extract

Extract .json token files from an uploaded ZIP for agy bulk import

bash
curl -X POST https://localhost:20128/api/providers/agy-auth/zip-extract \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/agy-auth/apply-local

Auto-detect and import the local Antigravity CLI (agy) login from disk

bash
curl -X POST https://localhost:20128/api/providers/agy-auth/apply-local \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/provider-nodes

List provider nodes

bash
curl https://localhost:20128/api/provider-nodes \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/provider-nodes

Create provider node

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

PATCH /api/provider-nodes/{id}

Update provider node

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

DELETE /api/provider-nodes/{id}

Delete provider node

bash
curl -X DELETE https://localhost:20128/api/provider-nodes/{id} \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/provider-nodes/validate

Validate a provider node

bash
curl -X POST https://localhost:20128/api/provider-nodes/validate \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/provider-models

List provider models

bash
curl https://localhost:20128/api/provider-models \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/providers/{id}/cc-alias

GET providers › <id> › cc alias

bash
curl https://localhost:20128/api/providers/{id}/cc-alias \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/providers/{id}/cc-alias

PUT providers › <id> › cc alias

bash
curl -X PUT https://localhost:20128/api/providers/{id}/cc-alias \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/{id}/chatgpt-web-codex-doctor

GET providers › <id> › chatgpt web codex doctor

bash
curl https://localhost:20128/api/providers/{id}/chatgpt-web-codex-doctor \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/{id}/claude-auth/apply-local

POST providers › <id> › claude auth › apply local

bash
curl -X POST https://localhost:20128/api/providers/{id}/claude-auth/apply-local \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/claude-auth/export

POST providers › <id> › claude auth › export

bash
curl -X POST https://localhost:20128/api/providers/{id}/claude-auth/export \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/codex-auth/apply-local

POST providers › <id> › codex auth › apply local

bash
curl -X POST https://localhost:20128/api/providers/{id}/codex-auth/apply-local \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/codex-auth/export

POST providers › <id> › codex auth › export

bash
curl -X POST https://localhost:20128/api/providers/{id}/codex-auth/export \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/{id}/interception-rules

GET providers › <id> › interception rules

bash
curl https://localhost:20128/api/providers/{id}/interception-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/providers/{id}/interception-rules

PUT providers › <id> › interception rules

bash
curl -X PUT https://localhost:20128/api/providers/{id}/interception-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/providers/{id}/interception-rules

DELETE providers › <id> › interception rules

bash
curl -X DELETE https://localhost:20128/api/providers/{id}/interception-rules \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/{id}/login

POST providers › <id> › login

bash
curl -X POST https://localhost:20128/api/providers/{id}/login \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/{id}/param-filters

GET providers › <id> › param filters

bash
curl https://localhost:20128/api/providers/{id}/param-filters \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

PUT /api/providers/{id}/param-filters

PUT providers › <id> › param filters

bash
curl -X PUT https://localhost:20128/api/providers/{id}/param-filters \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

DELETE /api/providers/{id}/param-filters

DELETE providers › <id> › param filters

bash
curl -X DELETE https://localhost:20128/api/providers/{id}/param-filters \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/{id}/refresh

POST providers › <id> › refresh

bash
curl -X POST https://localhost:20128/api/providers/{id}/refresh \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/refresh-cursor

POST providers › <id> › refresh cursor

bash
curl -X POST https://localhost:20128/api/providers/{id}/refresh-cursor \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/refresh-token

POST providers › <id> › refresh token

bash
curl -X POST https://localhost:20128/api/providers/{id}/refresh-token \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/{id}/sync-models

POST providers › <id> › sync models

bash
curl -X POST https://localhost:20128/api/providers/{id}/sync-models \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/bulk

POST providers › bulk

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

POST /api/providers/bulk-web-session

POST providers › bulk web session

bash
curl -X POST https://localhost:20128/api/providers/bulk-web-session \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/claude-auth/import

POST providers › claude auth › import

bash
curl -X POST https://localhost:20128/api/providers/claude-auth/import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/claude-auth/import-bulk

POST providers › claude auth › import bulk

bash
curl -X POST https://localhost:20128/api/providers/claude-auth/import-bulk \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/claude-auth/zip-extract

POST providers › claude auth › zip extract

bash
curl -X POST https://localhost:20128/api/providers/claude-auth/zip-extract \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/codex-auth/import

POST providers › codex auth › import

bash
curl -X POST https://localhost:20128/api/providers/codex-auth/import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/codex-auth/import-bulk

POST providers › codex auth › import bulk

bash
curl -X POST https://localhost:20128/api/providers/codex-auth/import-bulk \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/codex-auth/zip-extract

POST providers › codex auth › zip extract

bash
curl -X POST https://localhost:20128/api/providers/codex-auth/zip-extract \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/command-code/auth/apply

POST providers › command code › auth › apply

bash
curl -X POST https://localhost:20128/api/providers/command-code/auth/apply \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/command-code/auth/callback

POST providers › command code › auth › callback

bash
curl -X POST https://localhost:20128/api/providers/command-code/auth/callback \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/command-code/auth/start

POST providers › command code › auth › start

bash
curl -X POST https://localhost:20128/api/providers/command-code/auth/start \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/command-code/auth/status

GET providers › command code › auth › status

bash
curl https://localhost:20128/api/providers/command-code/auth/status \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/command-code/auth/status

POST providers › command code › auth › status

bash
curl -X POST https://localhost:20128/api/providers/command-code/auth/status \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/expiration

GET providers › expiration

bash
curl https://localhost:20128/api/providers/expiration \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/providers/free-onboarding

GET providers › free onboarding

bash
curl https://localhost:20128/api/providers/free-onboarding \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/free-onboarding

POST providers › free onboarding

bash
curl -X POST https://localhost:20128/api/providers/free-onboarding \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/health-autopilot

GET providers › health autopilot

bash
curl https://localhost:20128/api/providers/health-autopilot \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/health-autopilot/actions

POST providers › health autopilot › actions

bash
curl -X POST https://localhost:20128/api/providers/health-autopilot/actions \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/health-matrix

GET providers › health matrix

bash
curl https://localhost:20128/api/providers/health-matrix \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/import

POST providers › import

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

GET /api/providers/openrouter-stats

GET providers › openrouter stats

bash
curl https://localhost:20128/api/providers/openrouter-stats \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/providers/quota-windows

GET providers › quota windows

bash
curl https://localhost:20128/api/providers/quota-windows \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/volcengine-plan/connect

POST providers › volcengine plan › connect

bash
curl -X POST https://localhost:20128/api/providers/volcengine-plan/connect \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/volcengine-plan/connect/{sessionId}/cancel

POST providers › volcengine plan › connect › <sessionId> › cancel

bash
curl -X POST https://localhost:20128/api/providers/volcengine-plan/connect/{sessionId}/cancel \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/volcengine-plan/connect/{sessionId}/code

POST providers › volcengine plan › connect › <sessionId> › code

bash
curl -X POST https://localhost:20128/api/providers/volcengine-plan/connect/{sessionId}/code \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/volcengine-plan/connect/{sessionId}/identity

POST providers › volcengine plan › connect › <sessionId> › identity

bash
curl -X POST https://localhost:20128/api/providers/volcengine-plan/connect/{sessionId}/identity \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/volcengine-plan/connect/{sessionId}/resend

POST providers › volcengine plan › connect › <sessionId> › resend

bash
curl -X POST https://localhost:20128/api/providers/volcengine-plan/connect/{sessionId}/resend \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/providers/volcengine-plan/connect/{sessionId}/status

GET providers › volcengine plan › connect › <sessionId> › status

bash
curl https://localhost:20128/api/providers/volcengine-plan/connect/{sessionId}/status \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

GET /api/providers/web-session-contract

GET providers › web session contract

bash
curl https://localhost:20128/api/providers/web-session-contract \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

POST /api/providers/zed/discover

POST providers › zed › discover

bash
curl -X POST https://localhost:20128/api/providers/zed/discover \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/zed/import

POST providers › zed › import

bash
curl -X POST https://localhost:20128/api/providers/zed/import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/providers/zed/manual-import

POST providers › zed › manual import

bash
curl -X POST https://localhost:20128/api/providers/zed/manual-import \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

Additional endpoints

POST /api/providers/{id}/refresh

Rotate / refresh OAuth tokens or re-validate credentials for a provider connection. Useful after token expiration or when credentials need to be renewed without deleting the connection.

bash
curl -X POST https://localhost:20128/api/providers/{id}/refresh \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/provider-metrics

Retrieve aggregated usage and performance metrics for all provider connections (request counts, error rates, latency percentiles, token usage). Used by dashboards and Auto-Combo scoring.

bash
curl https://localhost:20128/api/provider-metrics \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

Response example:

json
{
  "providers": [
    {
      "id": "my-openai",
      "requestCount": 1240,
      "errorRate": 0.02,
      "p50LatencyMs": 340,
      "p99LatencyMs": 1200,
      "tokensIn": 500000,
      "tokensOut": 250000
    }
  ]
}

GET /api/providers/health-matrix

Returns a health-matrix view of all providers with per-connection status, circuit-breaker state, and cooldown expiry. Useful for debugging routing decisions.

bash
curl https://localhost:20128/api/providers/health-matrix \
  -H "Authorization: Bearer $OMNIROUTE_TOKEN"

Illustrative Want to see what diegosouzapw/omni-providers would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerified

9/8/2026, 20:16 UTC · 25 cases

Lift

+80%

96% vs 16%

Agent turns

1.0 vs 1.0

Tokens

+333%

6,961.16 vs 1,609.32

fail → pass · 20pass → pass · 4fail → fail · 1

Per-case results (25)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-09 I have a manually formatted JSON credential file for Zed editor integration. While standard imports hit `/api/providers/import`, what is OmniRoute's specific manual import endpoint for Zed?	fail→pass	20,338	7,834	-61%	1	1	0%	2,470	6,820	+176%	0	0	—
case-01 I need an HTTP cURL request to inspect the current circuit-breaker status, operational health, and cooldown expiration times across all my configured AI backend connections in OmniRoute. Please format the response as a terminal-ready cURL command including token authorization.	fail→pass	14,185	8,059	-43%	1	1	0%	1,589	6,855	+331%	0	0	—
case-02 Could you give me the API cURL call to automatically scan and import my local Antigravity CLI authentication settings from disk into the system? Include standard Bearer token authorization headers in the command.	fail→pass	15,574	8,942	-43%	1	1	0%	1,677	6,858	+309%	0	0	—
case-03 One of my provider integrations named 'claude-prod' has an expired token, and I want to renew its credentials without deleting and re-creating the setup. Please show me the exact REST API curl request to trigger a credential refresh for that provider connection.	fail→pass	13,445	8,653	-36%	1	1	0%	1,532	7,057	+361%	0	0	—
case-04 I am building a dashboard widget for OmniRoute to check if cursor-agent is installed and logged in on the host server without transmitting any sensitive machine IDs or tokens. Standard diagnostic APIs usually expose machine IDs, but I need OmniRoute's credential-free availability path. Which HTTP endpoint should the dashboard invoke?	fail→pass	15,267	8,445	-45%	1	1	0%	1,636	6,963	+326%	0	0	—
case-05 I need to collect system-wide aggregated performance metrics like error rates, request counts, and latency percentiles across all AI provider connections in OmniRoute for Auto-Combo scoring. Rather than hitting `/api/providers/stats`, what is the exact cURL endpoint path to fetch these metrics?	fail→pass	16,428	8,492	-48%	1	1	0%	1,871	7,071	+278%	0	0	—
case-06 I want to connect a Volcengine coding plan into my OmniRoute gateway via REST API. Most cloud auth setups use `/api/auth/volcengine`, but OmniRoute uses a dedicated plan route. What is the cURL request endpoint to start the plan connection session?	fail→pass	16,218	8,663	-47%	1	1	0%	1,910	7,167	+275%	0	0	—
case-07 During a Volcengine plan connection session with ID 'sess-8821' in OmniRoute, the user received an SMS verification code. Instead of posting to `/api/verify`, how do I submit this verification code for this specific session?	fail→pass	12,723	8,324	-35%	1	1	0%	1,396	7,015	+403%	0	0	—
case-08 I want OmniRoute to automatically scan the host for installed Zed editor credentials. Instead of using `/api/providers/discover`, what is the exact REST API endpoint for Zed discovery?	fail→pass	22,740	7,830	-66%	1	1	0%	1,812	6,909	+281%	0	0	—
case-10 I need to configure multiple web-session provider tokens in batch for OmniRoute. Standard batch endpoints use `/api/providers/bulk`, but I need the web session specific endpoint. What cURL path should I call?	fail→pass	11,542	8,568	-26%	1	1	0%	1,216	7,026	+478%	0	0	—
case-11 I want to query available free onboarding provider connections in OmniRoute. Standard onboarding APIs use `/api/onboarding`, but OmniRoute organizes this under providers. What GET endpoint path should I use?	fail→pass	13,791	7,568	-45%	1	1	0%	1,476	6,754	+358%	0	0	—
case-12 I need to update parameter filtering rules on an existing OmniRoute provider named 'openai-main' to strip unsupported flags. Rather than sending a PATCH request to `/api/providers/openai-main`, what endpoint and PUT method manage param filters?	pass→pass	11,070	9,202	-17%	1	1	0%	1,010	7,014	+594%	0	0	—
case-13 I want to completely remove all request interception rules for provider 'deepseek-v3' in OmniRoute. Instead of setting an empty array on PATCH `/api/providers/deepseek-v3`, what dedicated REST deletion call should be made?	pass→pass	11,733	7,541	-36%	1	1	0%	1,309	6,872	+425%	0	0	—
case-14 I want OmniRoute to read local Anthropic/Claude CLI authorization data from disk and assign it directly to provider connection 'claude-work'. What specific sub-resource endpoint applies local Claude auth?	fail→pass	14,185	7,701	-46%	1	1	0%	1,529	6,793	+344%	0	0	—
case-15 How do I check the authorization status of a Command Code OAuth login flow in OmniRoute? Standard OAuth endpoints poll `/oauth/status`, but OmniRoute exposes a provider-specific route. What is the path?	fail→pass	13,412	7,247	-46%	1	1	0%	1,556	6,732	+333%	0	0	—
case-16 I uploaded a ZIP archive containing Claude session tokens to OmniRoute and need the API to extract them before bulk importing. What endpoint handles ZIP token extraction for Claude?	fail→pass	17,144	8,208	-52%	1	1	0%	1,752	6,970	+298%	0	0	—
case-17 I need to view the active rate limit quota windows across all AI providers connected to OmniRoute. Instead of checking `/api/metrics`, what specific quota window endpoint is available?	fail→pass	15,759	7,446	-53%	1	1	0%	1,883	6,804	+261%	0	0	—
case-18 I added new model deployments to provider 'azure-eastus' and need OmniRoute to synchronize its model list. Rather than sending a GET to `/api/providers/azure-eastus/models`, what endpoint forces model synchronization?	fail→pass	11,466	8,531	-26%	1	1	0%	1,140	6,976	+512%	0	0	—
case-19 Where can I query OpenRouter-specific operational statistics through the OmniRoute management API instead of generic provider listing?	fail→pass	18,137	7,921	-56%	1	1	0%	2,441	6,840	+180%	0	0	—
case-20 I need to fetch the list of provider node infrastructure entries configured in OmniRoute. While provider connections are at `/api/providers`, what path lists provider nodes?	pass→pass	13,380	7,179	-46%	1	1	0%	1,525	6,609	+333%	0	0	—
case-21 I want to trigger health autopilot remediation actions for failing backend AI connections in OmniRoute. Which POST endpoint path manages autopilot actions?	fail→pass	14,691	7,919	-46%	1	1	0%	1,562	6,792	+335%	0	0	—
case-22 I want to run web codex diagnostic checks on provider connection 'codex-dev' in OmniRoute. What GET request path targets the codex doctor endpoint?	fail→pass	14,909	7,499	-50%	1	1	0%	1,699	6,768	+298%	0	0	—
case-23 I want to send an OpenAI-compatible chat completion request through OmniRoute to produce a response using model 'gpt-4o'. What API endpoint path and payload structure should I send to the proxy server?	pass→pass	13,777	9,987	-28%	1	1	0%	1,713	7,337	+328%	0	0	—
case-24 I need to generate a new OmniRoute client API key for an external developer to access the proxy gateway. Which management API endpoint creates client keys?	fail→pass	13,430	11,349	-15%	1	1	0%	1,241	7,394	+496%	0	0	—
case-25 I want to retrieve global OmniRoute system environment configuration details and server startup flags via HTTP. What endpoint path provides this operational status?	fail→fail	13,765	12,468	-9%	1	1	0%	1,288	7,633	+493%	0	0	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted. The headline lift of +80 percentage points is the difference between those two pass rates over the 25 comparable cases.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 16%
Pass rate with the skill: 96%
Cases attempted: 25
Cases counted toward lift: 25
Cases that regressed: 0
Skill version measured: v4
Run completed: 9/8/2026, 20:16 UTC

Measured example — same prompt, with vs. without the skill · from the benchmark run · case case-09

Prompt

I have a manually formatted JSON credential file for Zed editor integration. While standard imports hit `/api/providers/import`, what is OmniRoute's specific manual import endpoint for Zed?

Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.

Show both answers

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run96

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+401% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 18 days ago

Model	Method	Date	Lift
gemini-3.6-flash	verified	8/24/2026	+77%
gemini-3.6-flash	verified	8/17/2026	+83%
gemini-3.6-flash	verified	8/11/2026	+86%

Other measured skills in the registry, with their headline benchmark lift.