mcpField
C
cli-providers

cli-providers

github.com/cheaper-inferenceCloud & DevOps82.3k1.1k installsUpdated today
Repository

About cli-providers

cli-providers documents OmniRoute CLI commands for managing provider connections and keys. It includes catalog discovery, connection tests and validation, OAuth controls, metrics, and routing-combo management.

Key features

  1. 01Browse and filter provider catalog
  2. 02List, test, and validate connections
  3. 03Rotate provider credentials
  4. 04Manage OAuth provider sessions
  5. 05Inspect provider metrics and usage
  6. 06Create and switch routing combos

Use cases

  1. 01Find a provider by name or category
  2. 02Check configured connections before use
  3. 03Rotate credentials or review provider metrics
  4. 04Set a routing combo for failover

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cheaper-inference/omniroute --skill cli-providers

After installing, type/cli-providersin Claude Code to confirm it loaded.

Details

From the project README

Overview

Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.

Quick install

npm install -g omniroute   # or: npx omniroute
omniroute --version

Subcommands

provider-cmd provider [subcommand]

Manage provider connections (use

Example:

omniroute provider-cmd provider [subcommand]
providers

Example:

omniroute providers
providers available

Show available providers in the OmniRoute catalog

Flags:

  • --json
  • --search <query>
  • -q, --q <query>
  • --category <category>

Example:

omniroute providers available
providers list

List configured provider connections

Flags:

  • --json

Example:

omniroute providers list
providers test <idOrName>

Test a configured provider connection

Flags:

  • --json

Example:

omniroute providers test <idOrName>
providers test-all

Test all active provider connections

Flags:

  • --json

Example:

omniroute providers test-all
providers validate

Validate local provider configuration without calling upstream

Flags:

  • --json

Example:

omniroute providers validate
providers rotate <idOrName>

Flags:

  • --new-key <key>
  • --from-env <VAR>
  • --oauth
  • --yes
  • --skip-test
  • --dry-run

Example:

omniroute providers rotate <idOrName>
providers status

Flags:

  • --provider <name>
  • --json

Example:

omniroute providers status
providers metrics

Flags:

  • --provider <id>
  • --connection-id <id>
  • --period <p>
  • --metric <m>
  • --sort-by <field>
  • --limit <n>
  • --watch
  • --compare <list>

Example:

omniroute providers metrics
providers metric <connectionId> <metric>

Flags:

  • --period <p>

Example:

omniroute providers metric <connectionId> <metric>
test-provider test [provider] [model]

Flags:

  • --all-providers
  • --json
  • --latency
  • --repeat <n>
  • --compare <models>
  • --save <path>

Example:

omniroute test-provider test [provider] [model]

OmniRoute — CLI Providers & Keys

Requires the omniroute CLI. See CLI entry-point skill for install + global flags.

Provider catalog (available providers)

omniroute providers available                        # Full OmniRoute provider catalog
omniroute providers available --search openai        # Filter by id, name, alias
omniroute providers available --category api-key     # Filter by category
omniroute providers available --json                 # Machine-readable JSON

Categories: api-key, oauth, free, local, combo.

Configured provider connections

omniroute providers list                             # Connections in your DB
omniroute providers list --json

Testing connections

omniroute providers test <id|name>                   # Test one configured connection
omniroute providers test-all                         # Test every active connection (TUI progress)
omniroute providers validate                         # Local-only structural validation (no HTTP)

test-all opens an interactive TUI that shows live pass/fail per connection. Use --json to get a machine-readable result:

omniroute providers test-all --json

API key management (OmniRoute keys)

These manage the OmniRoute API keys issued under API Manager — not provider credentials.

omniroute keys list                                  # List all OmniRoute API keys
omniroute keys add <provider> [apiKey]               # Add an API key for a provider
omniroute keys remove <provider>                     # Remove an API key
omniroute keys regenerate <id>                       # Regenerate (rotate) a key
omniroute keys revoke <id>                           # Revoke a key (disables it)
omniroute keys reveal <id>                           # Show the full key value
omniroute keys usage <id>                            # Show usage stats for a key

omniroute keys rotate <id>                           # Rotate + revoke old key atomically
omniroute keys expiration list                       # List key expiration times
Key policies
omniroute keys policy show <id>                      # Show rate-limit / permission policy
omniroute keys policy set <id> \
  --rate-limit 100 \
  --rate-window minute \
  --permissions chat,models                          # Set policy on a key

Models

omniroute models                                     # List all models (all providers)
omniroute models openai                              # Filter by provider
omniroute models --search gpt                        # Search by name
omniroute models --json                              # JSON output

OAuth providers

omniroute oauth list                                 # List OAuth-configured providers
omniroute oauth login <provider>                     # Start browser-based OAuth flow
omniroute oauth logout <provider>                    # Revoke OAuth token
omniroute oauth status <provider>                    # Show token state + expiry
omniroute oauth refresh <provider>                   # Force token refresh

For OAuth providers (Gemini, Windsurf, Antigravity, etc.) the login command opens the OmniRoute dashboard OAuth flow in your browser.

Provider nodes (multi-account routing)

Provider nodes let you attach multiple API keys / accounts to one logical provider for round-robin or failover.

omniroute nodes list <provider>                      # List nodes for a provider
omniroute nodes add <provider> --api-key <key>       # Add a node
omniroute nodes remove <provider> <nodeId>           # Remove a node
omniroute nodes test <provider> <nodeId>             # Test one node

Routing combos (CLI)

Create and manage routing combos from the terminal:

omniroute combo list                                 # List all combos
omniroute combo create <name> \
  --strategy priority \
  --targets anthropic/claude-opus-4-7,openai/gpt-4o  # Create combo
omniroute combo switch <name>                        # Activate a combo as default
omniroute combo delete <name>                        # Delete a combo
omniroute combo suggest --task "code review"         # Ask OmniRoute to recommend a combo

For the full REST API for combos see omni-combos-routing skill.

Quota & usage

omniroute quota                                      # Provider quota usage + reset times
omniroute usage                                      # Request + token usage summary
omniroute cost                                       # Cost breakdown (by provider/model)

Compression (CLI)

omniroute compression status                         # Current compression mode + savings stats
omniroute compression set --mode rtk                 # Enable RTK compression
omniroute compression set --mode stacked             # Enable stacked (RTK + Caveman)
omniroute compression set --mode off                 # Disable compression
omniroute compression preview --mode rtk --text "..."  # Preview savings for sample text

Health

omniroute health                                     # Detailed health: circuit breakers, cache, memory

Errors

  • providers test <id> fails with 401 → API key stored for that provider is wrong; use keys remove + keys add to reset it
  • oauth login opens but doesn't complete → the OAuth token endpoint may be firewalled; use API key auth instead
  • combo create fails with strategy unknown → use one of: priority, weighted, round-robin, fill-first, least-used, cost-optimized, auto, random, strict-random, p2c, reset-aware, lkgp, context-optimized, context-relay

Comments

Markdown supported