omni-agents-a2a
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
<!-- 由 src/lib/agentSkills/generator.ts 生成;手动修改将被覆盖 -->
Overview
概述
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.
通过 JSON-RPC 2.0 Agent-to-Agent 协议与 OmniRoute 交互。内置 6 个 A2A skill:smart-routing、quota-management、provider-discovery、cost-analysis、health-report、list-capabilities。
Authentication
身份验证
All requests require a valid Bearer token or session cookie. Obtain a token via or configure for local development.
POST /api/auth/loginREQUIRE_API_KEY=false所有请求都需要有效的 Bearer token 或 session cookie。可通过 获取 token,或在本地开发环境中配置 。
POST /api/auth/loginREQUIRE_API_KEY=falseEndpoints
Endpoints
No endpoints mapped for this area yet.
此区域尚未映射 endpoint。
Payloads
Payload
See the full OpenAPI specification at or for detailed request/response schemas.
<!-- skill:custom-start -->
<!-- Migrated from skills/omniroute-a2a/SKILL.md (preserved curated content) -->GET /api/openapi/specdocs/openapi.yaml有关详细的请求/响应 schema,请参阅 处的完整 OpenAPI 规范或 。
<!-- skill:custom-start -->
<!-- 从 skills/omniroute-a2a/SKILL.md 迁移而来(保留精选内容) -->GET /api/openapi/specdocs/openapi.yamlOmniRoute — A2A Protocol
OmniRoute — A2A 协议
OmniRoute publishes an Agent Card at and accepts
JSON-RPC 2.0 calls at .
/.well-known/agent.json/a2aOmniRoute 在 发布 Agent Card,并接受发往 的 JSON-RPC 2.0 调用。
/.well-known/agent.json/a2aDiscovery
发现
bash
curl $OMNIROUTE_URL/.well-known/agent.jsonReturns Agent Card with skills, endpoints, auth scheme.
bash
curl $OMNIROUTE_URL/.well-known/agent.json返回包含 skills、endpoints 和认证方案的 Agent Card。
Available skills
可用 skills
| Skill | Purpose |
|---|---|
| Given a prompt, recommends best provider/model combo |
| Reports quota balance for given provider/account |
| Lists providers matching capability filters (vision, JSON mode, tools, max-context) |
| Estimates cost for a given request shape |
| Returns system health (circuit states, latencies, errors) |
| Skill | 用途 |
|---|---|
| 根据给定的 prompt,推荐最佳 provider/model 组合 |
| 报告指定 provider/account 的配额余额 |
| 列出符合能力筛选条件的 providers(vision、JSON mode、tools、max-context) |
| 估算给定请求形式的成本 |
| 返回系统健康状态(circuit 状态、延迟和错误) |
Call example (JSON-RPC 2.0)
调用示例(JSON-RPC 2.0)
bash
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
}'bash
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
}'Response shape
响应结构
json
{
"jsonrpc": "2.0",
"result": {
"taskId": "...",
"status": "completed",
"output": { "recommended_combo": "...", "reasoning": "..." }
},
"id": 1
}json
{
"jsonrpc": "2.0",
"result": {
"taskId": "...",
"status": "completed",
"output": { "recommended_combo": "...", "reasoning": "..." }
},
"id": 1
}Errors
错误
- → invalid request (bad JSON-RPC envelope)
-32600 - → method not found (check
-32601field)method - → invalid params (check
-32602against Agent Card)skillId - → missing/invalid
401OMNIROUTE_KEY
- → 请求无效(JSON-RPC envelope 无效)
-32600 - → 未找到方法(检查
-32601字段)method - → 参数无效(根据 Agent Card 检查
-32602)skillId - → 缺少或无效的
401OMNIROUTE_KEY
Reference
参考
<!-- skill:custom-end -->
<!-- skill:custom-end -->