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

Six tools, one loop.

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

01/06

  1. Credits accrue

    orbio_get_balance

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

  2. The agent claims

    orbio_claim_key

    Turns that balance into a funded OpenRouter key, up to $200.

  3. It watches the spend

    orbio_get_key_status

    Usage is read live from OpenRouter, never guessed at locally.

  4. Drawn down, so it tops up

    orbio_top_up_key

    Balance moves onto the same key, up to $200 unspent. The secret never changes.

  5. Leaked, so it rotates

    orbio_rotate_key

    A new secret with the same credit on it. The old one dies first.

  6. Or it pulls the plug

    orbio_delete_key

    One call disables the key. Whatever it had not spent comes back.

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.