Query OmniRoute through A2A, a protocol for communication between agents. Get provider and model recommendations, check remaining quotas, find providers with required features, estimate request costs, and review system health.
Interact with OmniRoute via JSON-RPC 2.0 agent-to-agent protocol. 6 built-in A2A skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities.
Query OmniRoute through A2A, which lets agents exchange information. Get suggestions for provider and model combinations that match a prompt’s requirements. Check remaining quotas by provider or account, find providers with the features you need, estimate request costs, and retrieve system health information. The published Agent Card shows available capabilities, connection endpoints, and authentication methods.
Use it to choose a connection based on requirements such as image input or tool use. It also helps when you want to check quotas and expected costs before running a request. An agent can use it to inspect system status, including response times and errors.
Set OMNIROUTE_URL and OMNIROUTE_KEY. Calls use JSON-RPC 2.0 and are sent to /a2a. Check the Agent Card for available capability identifiers and provide valid authentication credentials.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
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.
Review the instructions the agent will receive before you install.
Interact with OmniRoute via JSON-RPC 2.0 agent-to-agent protocol. 6 built-in A2A skills: smart-routing, quota-management, provider-discovery, cost-analysis, health-report, list-capabilities.
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.
No endpoints mapped for this area yet.
See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.
Requires OMNIROUTE_URL and OMNIROUTE_KEY. See entry-point SKILL for setup.
OmniRoute publishes an Agent Card at /.well-known/agent.json and accepts
JSON-RPC 2.0 calls at /a2a.
curl $OMNIROUTE_URL/.well-known/agent.json
Returns Agent Card with skills, endpoints, auth scheme.
| Skill | Purpose |
|---|---|
smart-routing | Given a prompt, recommends best provider/model combo |
quota-management | Reports quota balance for given provider/account |
provider-discovery | Lists providers matching capability filters (vision, JSON mode, tools, max-context) |
cost-analysis | Estimates cost for a given request shape |
health-report | Returns system health (circuit states, latencies, errors) |
curl -X POST $OMNIROUTE_URL/a2a \
-H "Authorization: Bearer $OMNIROUTE_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"method": "tasks/send",
"params": {
"skillId": "smart-routing",
"input": { "prompt_length": 4000, "tools": true, "vision": false }
},
"id": 1
}'
{
"jsonrpc": "2.0",
"result": {
"taskId": "...",
"status": "completed",
"output": { "recommended_combo": "...", "reasoning": "..." }
},
"id": 1
}
-32600 → invalid request (bad JSON-RPC envelope)-32601 → method not found (check method field)-32602 → invalid params (check skillId against Agent Card)401 → missing/invalid OMNIROUTE_KEYFull docs: https://github.com/diegosouzapw/OmniRoute/blob/main/docs/frameworks/A2A-SERVER.md
<!-- skill:custom-end -->No reviews yet. Tell others what you thought.
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.
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.
Back up and restore OmniRoute data from the command line. Covers incremental snapshots, encryption, cloud synchronization, scheduled backups, and archive import and export, with options for retention and previewing an import.
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.
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.
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.
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.