Orbio gives every account one API key with no spending limit and one lifetime usage number. Mesh sits in front of it: budgeted keys per agent, real cost attribution per request, and routing that downgrades instead of failing when a budget runs tight.
Orbio's own CREDIT trades below the $1 it converts to — live from the Exchange contract, updated as you read this.
Verified directly against Orbio's own API and MCP: one account, one key, no cap, one number.
The key spends the entire balance. One runaway agent, one bug, one bad prompt — and the whole account is exposed.
GET /api/v1/key returns one lifetime
used figure. No way to see which agent, task, or model spent what.
Converting CREDIT into spendable balance is a permanent burn, and CREDIT trades on a real market — sometimes at a discount, sometimes not.
No new infrastructure to learn — agents keep using an ordinary OpenAI-compatible client.
From the dashboard: an agent id, a dollar budget, a quality floor. Mesh returns a real, unguessable key — shown once, like any credential should be.
Any OpenAI-compatible SDK works unchanged: baseURL: ".../v1",
apiKey: "mesh_…". The agent never sees the real Orbio key.
Mesh reserves the worst-case cost before dispatch, downgrades the model if the budget's tight, forwards to Orbio, then books the real cost to that agent — verified against Orbio's own reported cost, not estimated.
Mesh polls Orbio's real balance alongside its own attribution, so drift between the two is visible on the dashboard — never silent.
Open the live dashboard to mint a key, watch real spend attribution, and see the provisioning signal reading straight from the chain.