The model you don't have to choose

One endpoint, every model, a council on demand

Today you pin a model at startup and swap it by hand. The Router removes that decision. It speaks the OpenAI protocol, so every tool that already talks to OpenAI talks to it unchanged — but instead of a human choosing the model, Agora chooses per request:

• Route one. A trivial fix goes to the cheapest capable model; a hard problem goes to the strongest. The pick comes from a bandit that learned which model wins which task class.
• Or convene many. For high-stakes classes — a review, a security audit, an architecture call — the Router fans the request out to several diverse model families and returns each answer as a separate choice. Uncorrelated minds, one request.
• Learn from reality. Where an answer can be checked — tests, lint, a merged PR — the verified result re-weights who to trust next time. The router gets wiser, not just busier.

A single model gives a single, confident, fragile answer. Agora gives structured choice that resolves to the right tool — and remembers what worked.

Why it's different

Routing is becoming a commodity. What isn't: a router that learns from your verified outcomes, runs on your own infrastructure, and leaves an audit trail you own. These five values are carried over straight from AGORA's principles (P1–P8).

Against the field

How a request is routed

The decision is echoed in both the response body (agora) and headers (X-Agora-Model, X-Agora-Task-Class, X-Agora-Route-Basis) — so you always know what answered and why.

1Get a key, then run one script

The Router is billed to your own key's budget — get one (self-service) and the scripts wire every agent for you.

Your key

Mint a personal key at https://agora-keys.legate.bot with your @payneteasy.com email. The Router needs scope route.complete and a budget — the default $5/mo key already has both. It looks like agk_live_….

One-shot setup script

The script sets your env vars and writes the config for Continue + Aider, and prints the two clicks for the GUI agents. It backs up every file it touches and deletes nothing.

macOS / Linux

export AGORA_KEY=agk_live_YOUR_KEY
curl -fsSL https://agorarouter.com/assets/agora-router-setup.sh -o agora-router-setup.sh
bash agora-router-setup.sh
source ~/.zshrc   # or ~/.bashrc

Windows · PowerShell

$env:AGORA_KEY = "agk_live_YOUR_KEY"
irm https://agorarouter.com/assets/agora-router-setup.ps1 -OutFile agora-router-setup.ps1
.\agora-router-setup.ps1

Smoke test

curl https://agora-mcp.legate.bot/v1/chat/completions \
  -H "Authorization: Bearer $AGORA_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"auto","messages":[{"role":"user","content":"Say hi in one word."}]}'

A clean reply carries an agora field showing the model it routed to. A 401 means the key/header is wrong; 402 no_billing_handle means the key has no budget.

2Per-agent configuration

If you'd rather wire one agent by hand. Everything below is just “OpenAI Compatible · this Base URL · this key · model auto”.

Cline / Roo Code GUI

In the provider dropdown choose OpenAI Compatible and fill:

Continue (VS Code / JetBrains)

Add to ~/.continue/config.yaml (the script writes this for you):

models:
  - name: AgoraRouter (auto)
    provider: openai
    model: auto
    apiBase: https://agora-mcp.legate.bot/v1
    apiKey: agk_live_YOUR_KEY
    roles: [chat, edit, apply]

Aider

export OPENAI_API_BASE=https://agora-mcp.legate.bot/v1
export OPENAI_API_KEY=agk_live_YOUR_KEY
aider --model openai/auto

Cursor

1. Settings → Models → enable OpenAI API Key.
2. Tick Override OpenAI Base URL → https://agora-mcp.legate.bot/v1.
3. Paste your agk_live_… key; add a custom model named auto.

Generic — OpenAI SDK

from openai import OpenAI
client = OpenAI(base_url="https://agora-mcp.legate.bot/v1",
                api_key="agk_live_YOUR_KEY")
r = client.chat.completions.create(
        model="auto",                      # the Router decides
        messages=[{"role":"user","content":"Refactor this loop."}])
print(r.choices[0].message.content)
print(r.model)                             # which model actually answered

3OpenAPI specification

The Router is fully described by an OpenAPI 3.1 document — two endpoints, POST /v1/chat/completions and GET /v1/models, with the Agora extensions (the model: "auto" contract, the X-Task-Class header, ensemble choices, and the agora decision record). Import it into Postman, Insomnia, an SDK generator, or any OpenAPI viewer.