Skip to content
cccskills
FreePublished on GitHub

cli-providers

Manage AI provider connections from the terminal. List configured services, test connections individually or together, rotate credentials, and inspect usage metrics. Validate local configuration without contacting providers when checking its structure.

OriginalShow the original description

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

See how to install

Good for

  • Test all active provider connections together
  • Validate configuration without external requests
  • Rotate provider credentials and manage OmniRoute API keys
  • Check provider usage, costs, and metrics

Files included (1)

  • SKILL.md8.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

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]
<!-- skill:custom-start --> <!-- Migrated from skills/omniroute-cli-providers/SKILL.md (preserved curated content) -->

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
<!-- skill:custom-end -->

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

cli-a2a

FreeSummary

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
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

cli-backup-sync

FreeSummary

Back up and restore OmniRoute data from the command line. Manage incremental snapshots, scheduled backups, encryption, and cloud synchronization, with options to compare differences and preview data transfers or imports before applying them.

  • Create a backup before restoring data
  • Schedule recurring backups
  • Compare differences before cloud synchronization
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

cli-batches

FreeSummary

Submit groups of AI requests as batch jobs with the OmniRoute command line. Manage input files, monitor or cancel jobs, save results and errors, and incorporate batch processing into automated build and deployment workflows.

  • Submitting AI requests from a JSONL file
  • Monitoring batch jobs and waiting for completion
  • Saving batch results and error details
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

cli-chat

FreeSummary

Send prompts to LLMs from a terminal, display answers as they arrive, or hold an ongoing conversation. Use files or standard input for prompts, choose models, and set system instructions through OmniRoute.

  • Sending a prompt from a terminal
  • Using file contents as a prompt
  • Displaying and saving streaming responses
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

cli-compression

FreeSummary

Configure prompt compression, which shortens text sent to AI models, through the OmniRoute command line. Adjust RTK filters, Caveman rules, and combined compression modes, then preview the results using real prompts.

  • Preview compression results with real prompts
  • Adjust RTK filters and Caveman rules
  • Compare combined compression modes
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

cli-contexts

FreeSummary

Manage OmniRoute context settings from the command line, including token budgets and RTK filters for processing context. Switch saved server connections, import or export configurations, and inspect or expire conversation sessions.

  • Adjust context token budgets and filtering rules
  • Switch between saved server connections
  • Import or export connection settings as JSON
diegosouzapw/OmniRoute78.2KUpdated Oct 18, 2026

See all skills by diegosouzapw

Report a problem with this skill