omniroute-cli-providers

Manage OmniRoute provider connections, API keys, OAuth tokens, and routing combos via CLI.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-cli-providers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniroute-cli-providers
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/skills/omniroute-cli-providers
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-cli-providers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you configure, troubleshoot, and optimize OmniRoute provider connections and routing behavior without manually editing configs or guessing which provider credentials are failing.

Core Features & Use Cases

  • Provider catalog & searching: List available providers by id/name/alias, category, or machine-readable JSON output.
  • Connection management & validation: Add, list, and test configured provider connections (including a TUI test-all and structural validation without HTTP).
  • API key and OAuth lifecycle: Manage OmniRoute API keys (add/remove/regenerate/revoke/reveal/rotate, usage, policy) and run OAuth login/logout/status/refresh for OAuth-based providers.
  • Routing combos & supporting tools: Create and switch routing combos, suggest combos for tasks, and manage provider nodes for multi-account round-robin or failover.
  • Operational visibility: Inspect quota, usage, cost breakdown, and compression settings from the CLI.

Quick Start

Ask the OmniRoute CLI to list all configured provider connections in JSON format.

Frequently Asked Questions about omniroute-cli-providers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage API keys and OAuth tokens for AI providers from the CLI?

Managing API keys and OAuth tokens from the CLI involves adding, removing, rotating, and revoking credentials to resolve provider authentication issues. This Skill handles the full OAuth lifecycle and API key rotation directly from the terminal.

Can I test AI provider connections and validate failover routing without sending HTTP requests?

Testing provider connections without HTTP requests is possible through structural validation and a TUI test-all command. This validates configured provider nodes and failover setups quickly before live traffic routing.

What is the best way to create and switch routing combos for model routing across multiple AI providers?

Creating and switching routing combos is done by generating task-specific suggestions and configuring provider nodes for multi-account round-robin. This enables dynamic model routing across various AI providers directly from the terminal.

How do I check API quota, usage, and cost breakdown for configured provider connections?

Checking API quota, usage, and cost breakdown requires operational visibility commands in the OmniRoute CLI. This Skill inspects compression settings and cost metrics for all configured provider connections.

Do I need an operational OmniRoute CLI environment to list available providers by category?

An operational OmniRoute CLI environment with provider catalog access is required to list available providers by id, name, alias, or category. You need this CLI setup to search and output machine-readable JSON provider lists.

Why does my OmniRoute provider connection fail during key rotation or OAuth refresh?

Provider connection failures during key rotation or OAuth refresh often stem from invalid credentials or expired tokens. This Skill troubleshoots OmniRoute provider connections and runs OAuth status and refresh actions to resolve routing issues.