Remote MCP

Let your agent
keep itself funded💵

Orbio MCP lets your agent self-manage its credits and keys, with full control.

Connect an agent

The process

Five tools, one loop.

An agent runs the whole cycle on the same code the dashboard uses.

01/05

  1. Credits accrue

    orbio_get_balance

    A share of every trading fee, split across holders, every hour.

  2. The agent creates a key

    orbio_create_key

    One Orbio key that spends the balance live at the gateway. Nothing to top up, ever.

  3. It watches the spend

    orbio_get_key_status

    Every request is charged at the price OpenRouter states, and the balance is the quota.

  4. Leaked, so it replaces it

    orbio_create_key

    A new secret; the old one stops in the same statement. The credit never moved.

  5. Or it pulls the plug

    orbio_revoke_key

    One call stops the key on the next request. The balance stays exactly where it is.

Register the endpoint, then run /mcp inside Claude Code. It marks the server as needing sign-in the moment our server answers 401, and opens the browser for you.

terminal
claude mcp add --transport http --scope user orbio https://www.orbio.so/api/mcp
in claude code
/mcp        # pick orbio, then Authenticate

--scope user is the point: credits belong to your account, not to one repository, so the agent can top itself up wherever it is working. Drop it to limit the connection to the current project.