FreePublished on GitHubEnglish overview

omni-providers

Manage AI service connections in OmniRoute through its REST API. Add, update, remove, and test connections, refresh authentication credentials, and inspect usage, errors, response times, and connection health to investigate routing behavior.

OriginalShow the original description

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 375-provider catalog.

cheaper-inference/OmniRoute

AI rating70/ 100 See how to install

Good for

Add or update an AI service connection
Refresh credentials after token expiration
Run individual or batch connection tests
Inspect usage, response times, and connection health

Overview

What it does

Manage the AI service connections registered in OmniRoute through its API. You can list, add, update, and delete connections, manage authentication with API keys or OAuth, and test connections individually or in batches. The skill also covers refreshing credentials without deleting a connection and checking the models available from each service.

When it helps

Use it to manage connections when working with several AI services through OmniRoute. It also helps when tokens expire or you want to investigate why a particular connection was selected. You can inspect aggregate request counts, error rates, response times, and token usage, as well as the status of individual connections.

Example requests

“List the registered AI services and test the connection I specify.”
“Refresh the expired OAuth token without deleting the connection.”
“Check the error rate, response time, and health of each connection.”

Notes

Access to the OmniRoute API requires a valid Bearer token or session cookie. Authentication for connected services involves API keys or OAuth. Detailed request and response formats for each API are available through GET /api/openapi/spec or in docs/openapi.yaml.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?: AGoodThe overview explicitly identifies connection creation, updates, deletion, testing, and authentication management.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?: BPartly lackingAPI endpoints and reference links are listed, but the supplied excerpt contains no concrete request or response examples.
SafetyAre sending data, deleting files, and running commands disclosed?: BPartly lackingDeletion and credential import/export endpoints are listed, but the supplied excerpt gives no confirmation procedure before execution.
Easy setupDoes it need few tools or API keys, and are they documented?: BPartly lackingA token acquisition endpoint is provided, but installation instructions for OmniRoute itself are absent.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 22, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Files included (2)

SKILL.md9.8 KB
references/endpoints.md27.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 375-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

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.

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.

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

Response example:

{
  "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.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

More skills from this repository

cli-a2a

FreeSummaryAI rating 90

Use the command line to send tasks to OmniRoute's A2A server, which supports communication between agents. Inspect execution history and logs, monitor or cancel tasks, and interactively test the JSON-RPC 2.0 communication protocol.

Check server status and available skills
Invoke a skill with JSON input
Inspect task history and logs