Remote MCP

Let your agent
keep itself funded

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

The process

Five tools, one loop.

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

01/05

  1. Credits accrue

    ponbit_get_balance

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

  2. The agent claims

    ponbit_claim_key

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

  3. It watches the spend

    ponbit_get_key_status

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

  4. Spent, so it rotates

    ponbit_rotate_key

    Keys are never topped up. Drawn down, retired, replaced.

  5. Or it pulls the plug

    ponbit_revoke_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 ponbit https://ponbit.app/api/mcp
in claude code
/mcp        # pick ponbit, 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.