docs(i18n): apply deep machine translation to 33 languages

This commit is contained in:
diegosouzapw 2026-04-06 18:14:01 -03:00
parent 5085dcf96f
commit fa886231d3
466 changed files with 92226 additions and 147160 deletions

View file

@ -4,11 +4,9 @@
---
> **Agent-to-Agent Protocol v0.3** — Enables any AI agent to use OmniRoute as an intelligent routing agent via JSON-RPC 2.0.
> **Agent-to-Agent Protocol v0.3**— Nagbibigay-daan sa sinumang ahente ng AI na gamitin ang OmniRoute bilang isang intelligent na ahente sa pagruruta sa pamamagitan ng JSON-RPC 2.0.
The A2A Server exposes OmniRoute as a **first-class agent** that other agents can discover, delegate tasks to, and collaborate with using the [A2A Protocol](https://google.github.io/A2A/).
---
Inilalantad ng A2A Server ang OmniRoute bilang isang**first-class agent**na maaaring matuklasan ng ibang mga ahente, magtalaga ng mga gawain, at makipagtulungan sa paggamit ng [A2A Protocol](https://google.github.io/A2A/).---
## Arkitektura
@ -43,15 +41,12 @@ The A2A Server exposes OmniRoute as a **first-class agent** that other agents ca
### Agent Discovery
Every A2A-compatible agent exposes an **Agent Card** at `/.well-known/agent.json`:
```bash
Ang bawat A2A-compatible na ahente ay naglalantad ng**Agent Card**sa `/.well-known/agent.json`:```bash
curl http://localhost:20128/.well-known/agent.json
```
**Response:**
````
```json
**Tugon:**```json
{
"name": "OmniRoute",
"description": "Intelligent AI gateway with auto-routing across 50+ providers",
@ -88,7 +83,7 @@ curl http://localhost:20128/.well-known/agent.json
"apiKeyHeader": "Authorization"
}
}
```
````
---
@ -96,27 +91,24 @@ curl http://localhost:20128/.well-known/agent.json
### `message/send` — Synchronous Execution
Send a message to a skill and receive the complete response.
```bash
Magpadala ng mensahe sa isang kasanayan at tanggapin ang kumpletong tugon.```bash
curl -X POST http://localhost:20128/a2a \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "message/send",
"params": {
"skill": "smart-routing",
"messages": [{"role": "user", "content": "Write a Python hello world"}],
"metadata": {"model": "auto", "combo": "fast-coding"}
}
}'
```
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "message/send",
"params": {
"skill": "smart-routing",
"messages": [{"role": "user", "content": "Write a Python hello world"}],
"metadata": {"model": "auto", "combo": "fast-coding"}
}
}'
**Response:**
````
```json
**Tugon:**```json
{
"jsonrpc": "2.0",
"id": "1",
@ -133,36 +125,33 @@ curl -X POST http://localhost:20128/a2a \
}
}
}
```
````
### `message/stream` — SSE Streaming
Same as `message/send` but returns Server-Sent Events for real-time streaming.
```bash
Kapareho ng `mensahe/ipadala` ngunit ibinabalik ang Mga Kaganapang Ipinadala ng Server para sa real-time na streaming.```bash
curl -N -X POST http://localhost:20128/a2a \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "message/stream",
"params": {
"skill": "smart-routing",
"messages": [{"role": "user", "content": "Explain quantum computing"}]
}
}'
```
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_KEY" \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "message/stream",
"params": {
"skill": "smart-routing",
"messages": [{"role": "user", "content": "Explain quantum computing"}]
}
}'
**SSE Events:**
````
```
**Mga Kaganapan sa SSE:**```
data: {"jsonrpc":"2.0","method":"message/stream","params":{"task":{"id":"...","state":"working"},"chunk":{"type":"text","content":"Quantum computing..."}}}
: heartbeat 2026-03-04T21:00:00Z
data: {"jsonrpc":"2.0","method":"message/stream","params":{"task":{"id":"...","state":"completed"},"metadata":{...}}}
```
````
### `tasks/get` — Query Task Status
@ -188,40 +177,36 @@ curl -X POST http://localhost:20128/a2a \
### `smart-routing`
Routes prompts through OmniRoute's intelligent pipeline with full observability.
Ang mga ruta ay nag-uudyok sa pamamagitan ng intelligent na pipeline ng OmniRoute na may ganap na pagmamasid.
**Parameters (in `metadata`):**
**Mga Parameter (sa `metadata`):**
| Parameter | Type | Default | Description |
| --------- | -------- | ------------ | ---------------------------------------------------------------------------------------- |
| `model` | `string` | `"auto"` | Target model (e.g., `claude-sonnet-4`, `gpt-4o`, `auto`) |
| `combo` | `string` | active combo | Specific combo to route through |
| `budget` | `number` | none | Maximum cost in USD for this request |
| `role` | `string` | none | Task role hint: `coding`, `review`, `planning`, `analysis`, `debugging`, `documentation` |
| Parameter | Uri | Default | Paglalarawan |
| ---------- | -------- | -------------- | ---------------------------------------------------------------------------------------------------------- |
| `modelo` | `string` | `"awto"` | Target na modelo (hal., `claude-sonnet-4`, `gpt-4o`, `auto`) |
| `combo` | `string` | aktibong combo | Tukoy na combo na dadaan sa |
| `badyet` | `numero` | wala | Pinakamataas na halaga sa USD para sa kahilingang ito |
| `gampanin` | `string` | wala | Pahiwatig ng tungkulin ng gawain: `coding`, `review`, `planning`, `analysis`, `debugging`, `documentation` |
**Returns:**
**Pagbabalik:**
| Field | Description |
| ------------------------------ | --------------------------------------------------------- |
| `artifacts[].content` | The LLM response text |
| `metadata.routing_explanation` | Human-readable explanation of routing decision |
| `metadata.cost_envelope` | Estimated vs actual cost with currency |
| `metadata.resilience_trace` | Array of events (primary_selected, fallback_needed, etc.) |
| `metadata.policy_verdict` | Whether the request was allowed and why |
| Patlang | Paglalarawan |
| ------------------------------ | ----------------------------------------------------------------- | ---------------------- |
| `artifacts[].content` | Ang teksto ng tugon ng LLM |
| `metadata.routing_explanation` | Nababasa ng tao na paliwanag ng desisyon sa pagruruta |
| `metadata.cost_envelope` | Tinantyang vs aktwal na gastos sa currency |
| `metadata.resilience_trace` | Array ng mga kaganapan (primary_selected, fallback_needed, atbp.) |
| `metadata.policy_verdict` | Kung pinayagan ang kahilingan at bakit | ### `quota-management` |
### `quota-management`
Sumasagot sa mga query sa natural na wika tungkol sa mga quota ng provider.
Answers natural-language queries about provider quotas.
**Mga uri ng query (hinuha mula sa nilalaman ng mensahe):**
**Query types (inferred from message content):**
| Query Pattern | Response Type |
| ---------------------------------------------- | -------------------------------------------------------- |
| Contains `"ranking"`, `"most quota"`, `"best"` | Providers ranked by remaining quota |
| Contains `"free"`, `"suggest"` | Lists free combos or suggests free-tier providers |
| Default | Full quota summary with warnings for low-quota providers |
---
| Pattern ng Query | Uri ng Tugon |
| ------------------------------------------------------------- | ------------------------------------------------------------------------------ | --- |
| Naglalaman ng `"ranggo"`, `"pinaka quota"`, `"pinakamahusay"` | Niraranggo ang mga provider ayon sa natitirang quota |
| Naglalaman ng `"libre"`, `"suggest"` | Naglilista ng mga libreng combo o nagmumungkahi ng mga free-tier na provider |
| Default | Buong buod ng quota na may mga babala para sa mga provider na mababa ang quota | --- |
## Task Lifecycle
@ -231,19 +216,17 @@ submitted ──→ working ──→ completed
──────────→ cancelled
```
| State | Description |
| ----------- | ----------------------------------------------------- |
| `submitted` | Task created, queued for execution |
| `working` | Skill handler is executing |
| `completed` | Execution succeeded, artifacts available |
| `failed` | Execution failed or task expired (TTL: 5 min default) |
| `cancelled` | Cancelled by client via `tasks/cancel` |
| Estado | Paglalarawan |
| -------------- | -------------------------------------------------------------------- |
| `naisumite` | Nagawa ang gawain, nakapila para sa pagpapatupad |
| `nagtatrabaho` | Ang handler ng kasanayan ay nagsasagawa ng |
| `nakumpleto` | Nagtagumpay ang pagpapatupad, magagamit ang mga artifact |
| `nabigo` | Nabigo ang pagpapatupad o nag-expire ang gawain (TTL: 5 min default) |
| `kinansela` | Kinansela ng kliyente sa pamamagitan ng `tasks/cancel` |
- Terminal states: `completed`, `failed`, `cancelled` (no further transitions)
- Expired tasks in `submitted` or `working` are auto-marked as `failed`
- Tasks are garbage-collected after 2× TTL
---
- Terminal states: `completed`, `failed`, `cancelled` (walang karagdagang transition)
- Ang mga nag-expire na gawain sa `isumite` o `gumagana` ay awtomatikong minarkahan bilang `bigo`
- Ang mga gawain ay kinokolekta ng basura pagkatapos ng 2× TTL---
## Client Examples
@ -541,15 +524,12 @@ func main() {
### 🤖 Use Case 1: Multi-Agent Coding Pipeline
An orchestrator agent delegates code generation to OmniRoute, then passes the output to a review agent.
```python
def coding_pipeline(task: str):
# Step 1: Generate code via OmniRoute A2A
code_result = a2a_send("smart-routing", [
{"role": "user", "content": f"Write production-quality code: {task}"}
], metadata={"model": "auto", "role": "coding"})
code = code_result["artifacts"][0]["content"]
Ang isang ahente ng orkestra ay nagtatalaga ng pagbuo ng code sa OmniRoute, pagkatapos ay ipinapasa ang output sa isang ahente ng pagsusuri.```python
def coding_pipeline(task: str): # Step 1: Generate code via OmniRoute A2A
code_result = a2a_send("smart-routing", [
{"role": "user", "content": f"Write production-quality code: {task}"}
], metadata={"model": "auto", "role": "coding"})
code = code_result["artifacts"][0]["content"]
# Step 2: Review the code via OmniRoute A2A (different model)
review_result = a2a_send("smart-routing", [
@ -562,13 +542,12 @@ def coding_pipeline(task: str):
print(f"Review cost: ${review_result['metadata']['cost_envelope']['actual']}")
return {"code": code, "review": review}
```
````
### 💡 Use Case 2: Quota-Aware Agent Swarm
Multiple agents share quota through OmniRoute, using the quota skill to coordinate.
```python
Maraming ahente ang nagbabahagi ng quota sa pamamagitan ng OmniRoute, gamit ang kakayahan sa quota para mag-coordinate.```python
async def quota_aware_agent(agent_name: str, task: str):
# Check quota before starting
quota = a2a_send("quota-management", [
@ -591,32 +570,30 @@ async def quota_aware_agent(agent_name: str, task: str):
print(f"[{agent_name}] Free alternatives: {quota['artifacts'][0]['content']}")
return result
```
````
### 📊 Use Case 3: Real-Time Streaming Dashboard
A monitoring agent streams responses and displays progress in real-time.
```typescript
Ang isang ahente sa pagsubaybay ay nag-stream ng mga tugon at nagpapakita ng pag-unlad sa real-time.```typescript
async function streamingDashboard(prompt: string) {
const response = await fetch(`${BASE_URL}/a2a`, {
method: "POST",
headers: { "Content-Type": "application/json", Authorization: `Bearer ${API_KEY}` },
body: JSON.stringify({
jsonrpc: "2.0",
id: "dash-1",
method: "message/stream",
params: { skill: "smart-routing", messages: [{ role: "user", content: prompt }] },
}),
});
body: JSON.stringify({
jsonrpc: "2.0",
id: "dash-1",
method: "message/stream",
params: { skill: "smart-routing", messages: [{ role: "user", content: prompt }] },
}),
});
let totalChunks = 0;
const reader = response.body!.getReader();
const decoder = new TextDecoder();
let totalChunks = 0;
const reader = response.body!.getReader();
const decoder = new TextDecoder();
while (true) {
const { done, value } = await reader.read();
if (done) break;
while (true) {
const { done, value } = await reader.read();
if (done) break;
for (const line of decoder.decode(value).split("\n")) {
if (line.startsWith("data: ")) {
@ -640,15 +617,15 @@ async function streamingDashboard(prompt: string) {
}
}
}
}
}
```
}
````
### 🔁 Use Case 4: Task Polling Pattern
For long-running tasks, poll the task status instead of waiting synchronously.
```python
Para sa mga matagal nang gawain, i-poll ang status ng gawain sa halip na maghintay nang sabay-sabay.```python
import time
def poll_task(task_id: str, timeout: int = 60):
@ -678,75 +655,71 @@ def poll_task(task_id: str, timeout: int = 60):
"params": {"taskId": task_id},
})
raise TimeoutError(f"Task {task_id} timed out after {timeout}s")
```
````
---
## Error Codes
| Code | Constant | Meaning |
| ------ | ------------------------ | ---------------------------------------- |
| -32700 | — | Parse error (invalid JSON) |
| -32600 | `INVALID_REQUEST` | Invalid JSON-RPC request or unauthorized |
| -32601 | `METHOD_NOT_FOUND` | Unknown method or skill |
| -32602 | `INVALID_PARAMS` | Missing or invalid parameters |
| -32603 | `INTERNAL_ERROR` | Skill execution failed |
| -32001 | `TASK_NOT_FOUND` | Task ID not found |
| -32002 | `TASK_ALREADY_COMPLETED` | Cannot modify a completed task |
| -32003 | `UNAUTHORIZED` | Invalid or missing API key |
| -32004 | `BUDGET_EXCEEDED` | Request exceeds configured budget |
| -32005 | `PROVIDER_UNAVAILABLE` | No available providers |
---
| Code | pare-pareho | Ibig sabihin |
| ------ | ------------------------ | ------------------------------------------------------ | --- |
| -32700 | — | Error sa pag-parse (di-wastong JSON) |
| -32600 | `INVALID_REQUEST` | Di-wastong kahilingan sa JSON-RPC o hindi awtorisadong |
| -32601 | `METHOD_NOT_FOUND` | Hindi alam na paraan o kasanayan |
| -32602 | `INVALID_PARAMS` | Nawawala o di-wastong mga parameter |
| -32603 | `INTERNAL_ERROR` | Nabigo ang pagpapatupad ng kasanayan |
| -32001 | `GAWAIN_HINDI_NATAGPUAN` | Hindi nakita ang Task ID |
| -32002 | `KUMPLETO_MAG-GAWAIN` | Hindi mabago ang isang nakumpletong gawain |
| -32003 | `HINDI AUTHORIZED` | Di-wasto o nawawala ang API key |
| -32004 | `BUDGET_EXCEEDED` | Ang kahilingan ay lumampas sa naka-configure na badyet |
| -32005 | `PROVIDER_UNAVAILABLE` | Walang available na provider | --- |
## Authentication
All `/a2a` requests require a Bearer token via the `Authorization` header:
```
Lahat ng hiling na `/a2a` ay nangangailangan ng isang Bearer token sa pamamagitan ng header ng `Authorization`:```
Authorization: Bearer YOUR_OMNIROUTE_API_KEY
```
If no API key is configured on the server (`OMNIROUTE_API_KEY` is empty), authentication is bypassed.
---
Kung walang API key na naka-configure sa server (ang `OMNIROUTE_API_KEY` ay walang laman), ang pagpapatotoo ay na-bypass.---
## File Structure
```
src/lib/a2a/
├── taskManager.ts # Task lifecycle (create/update/cancel/list), TTL, cleanup
├── taskExecution.ts # Generic task executor with state management
├── streaming.ts # SSE stream formatting, heartbeat, chunk/completion events
├── routingLogger.ts # Routing decision logger (stats, history, retention)
├── taskManager.ts # Task lifecycle (create/update/cancel/list), TTL, cleanup
├── taskExecution.ts # Generic task executor with state management
├── streaming.ts # SSE stream formatting, heartbeat, chunk/completion events
├── routingLogger.ts # Routing decision logger (stats, history, retention)
└── skills/
├── smartRouting.ts # Smart routing skill (routes via /v1/chat/completions)
└── quotaManagement.ts # Quota management skill (natural-language quota queries)
├── smartRouting.ts # Smart routing skill (routes via /v1/chat/completions)
└── quotaManagement.ts # Quota management skill (natural-language quota queries)
src/app/a2a/
└── route.ts # Next.js API route handler (JSON-RPC 2.0 dispatch)
└── route.ts # Next.js API route handler (JSON-RPC 2.0 dispatch)
open-sse/mcp-server/
└── schemas/a2a.ts # Zod schemas (AgentCard, Task, JSON-RPC, SSE events)
└── schemas/a2a.ts # Zod schemas (AgentCard, Task, JSON-RPC, SSE events)
```
---
## Comparison: MCP vs A2A
| Feature | MCP Server | A2A Server |
| Tampok | MCP Server | A2A Server |
| ----------------- | ---------------------------- | ------------------------------------------------- |
| **Protocol** | Model Context Protocol | Agent-to-Agent Protocol v0.3 |
| **Transport** | stdio / HTTP | HTTP (JSON-RPC 2.0) |
| **Discovery** | Tool listing via MCP | `/.well-known/agent.json` |
| **Granularity** | 16 individual tools | 2 high-level skills |
| **Best for** | IDE agents (Cursor, VS Code) | Multi-agent systems (LangChain, CrewAI) |
| **Streaming** | Not supported | SSE via `message/stream` |
| **Task tracking** | No | Full lifecycle (submitted → completed) |
| **Observability** | Audit log per tool call | Cost envelope + resilience trace + policy verdict |
---
|**Protocol**| Model Context Protocol | Agent-to-Agent Protocol v0.3 |
|**Sasakyan**| stdio / HTTP | HTTP (JSON-RPC 2.0) |
|**Pagtuklas**| Listahan ng tool sa pamamagitan ng MCP | `/.well-known/agent.json` |
|**Granularity**| 16 indibidwal na tool | 2 mataas na antas ng kasanayan |
|**Pinakamahusay para sa**| Mga ahente ng IDE (Cursor, VS Code) | Multi-agent system (LangChain, CrewAI) |
|**Pag-stream**| Hindi suportado | SSE sa pamamagitan ng `mensahe/stream` |
|**Pagsubaybay sa gawain**| Hindi | Buong lifecycle (naisumite → nakumpleto) |
|**Pagmamasid**| Audit log sa bawat tool call | Sobre ng gastos + bakas ng katatagan + hatol ng patakaran |---
## Lisensya
Part of [OmniRoute](https://github.com/diegosouzapw/OmniRoute) — MIT License.
Bahagi ng [OmniRoute](https://github.com/diegosouzapw/OmniRoute) — Lisensya ng MIT.
```