Data & AI · wired today

What can agents actually do with OpenRouter?

Models and datasets are infrastructure now, and agents need eyes on them. The OpenRouter connector is one of 222 executable connectors and gives agents 4 tools, with the credential held in the vault and every call receipted.

The OpenRouter tool list, exactly as agents see it

get_key — Get the OpenRouter API key's own account info: label, current usage, credit limit and whether it is a free-tier key. The cheap balance/limits read and the spec's auth-proving call
list_models — List every model routable through OpenRouter's 300+ model catalogue, with context length and per-token pricing. Publicly readable, this endpoint answers even without a valid key
get_credits — Get the OpenRouter account's prepaid credit balance: total credits purchased and total credits used so far
chat_completion — Send a chat completion to any OpenRouter-routed model. This spends the account's prepaid credits, so it is HITL-gated and never fired by the shape-proof harness (write:true means blind proof always SKIPs it; a real credential would also need --include-writes)

What the OpenRouter connector needs

You provide API key from your OpenRouter account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: OpenRouter's own API documentation ↗ covers creating and scoping the credential.

How proven is this?

This connector was blind shape-proven against the real OpenRouter API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
Approvable Its write tools execute only after a human approves them in the inbox.
Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.

OpenRouter integration FAQ

What can Quox agents do with OpenRouter?

Agents can run 4 tools against OpenRouter: get key, list models, get credits, chat completion. Every call is receipted in the evidence trail.

What does the OpenRouter integration need?

You provide API key from your OpenRouter account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my OpenRouter credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the OpenRouter connector?