PinkWallet Website Logo
Join early access
Coding agent · AnthropicSign in or agent keyAbout 1 minVerified 2026-10-01

Connect Claude Code to Pink Agentic AI Payments

One command registers Pink as an MCP server in Claude Code; sign in with /mcp or use an agent key directly. Works with Claude Code in the terminal, the desktop app and IDE extensions. Plans: Any Claude Code plan.

What you get

Claude Code asks Pink before it pays

Once connected, Claude Code can see its budget, the payees it may pay and the rules that apply, run a dry run, request a payment and file the receipt. The rules you set in Pink decide each request: allowed on the spot, sent to a person on the phone, or blocked. Claude Code never holds a card number or a bank login.

Step by step

  1. 1

    Create a free sandbox workspace

    Open agentic-sandbox.pinkwallet.com, type a company name, pick a template (coffee shop, startup or e-commerce) and click Create workspace. You get an admin key for the console and one key per AI agent. Keep the admin key: the sign-in page asks for it.
    After creating a workspace: the admin key and one key per agent are shown once
    After creating a workspace: the admin key and one key per agent are shown once
  2. 2

    Register Pink from the terminal

    Run claude mcp add --transport http pink https://agentic-sandbox.pinkwallet.com/mcp. For a project-only setup add --scope project, which writes a .mcp.json you can commit.
  3. 3

    Sign in

    Start Claude Code, type /mcp, select pink and choose Authenticate. Your browser opens Pink's sign-in page.
  4. 4

    Sign in on Pink's page and pick the agent

    Claude Code opens Pink's sign-in page. Paste your admin key, choose which agent Claude Code should act as (for example Purchasing AI), then click Allow. From now on Claude Code holds a token for that one agent, never a card number or a bank login.
    Pink's sign-in page: paste the admin key, choose which agent the app acts as, click Allow
    Pink's sign-in page: paste the admin key, choose which agent the app acts as, click Allow
  5. 5

    Or skip the sign-in with an agent key

    For scripts and CI, register with the key in the URL instead: claude mcp add --transport http pink https://agentic-sandbox.pinkwallet.com/mcp/<agent_key>. No browser step; the key identifies the agent.
    After creating a workspace: the admin key and one key per agent are shown once
    After creating a workspace: the admin key and one key per agent are shown once
  6. 6

    Ask it to buy something

    In the session, describe the purchase. Claude Code calls the Pink tools and prints the decision. Blocked and pending requests say why.
  7. 7

    Watch the approval land in the console

    Open the sandbox console (link on the workspace page). Requests that cleared, asked a person or were blocked are all listed with the rule that decided them. Approve the pending one and the agent continues.
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence

The configuration, ready to paste

Claude Code · bash
claude mcp add --transport http pink https://agentic-sandbox.pinkwallet.com/mcp
# then inside Claude Code:
/mcp        # select pink → Authenticate

# or, without a browser step (scripts, CI):
claude mcp add --transport http pink https://agentic-sandbox.pinkwallet.com/mcp/<agent_key>

Replace <agent_key> with the key of the agent this coding agent should act as. Each agent has its own key, budget and rules.

Try it: say this to Claude Code

Say this

“Check my budget with Pink, then order 20 kg of espresso beans from Counter Culture Coffee for $420. After that, order $890 of weekly supplies from Sysco.”

What you will see

The first order is allowed on the spot and the agent receives a single-use test credential. The second stops at the store manager's rule ($500–$2,000): it shows up under Approvals in the console, and the agent waits for a person. Approve it there and the agent picks up the credential.

Why those two rules exist →

Pink's side, in three screens

The sandbox workspace page with the admin key and one key per agent
Keys are shown once when the workspace is created.
Pink's sign-in page: admin key, agent selector, Allow and Deny
Sign-in: choose which agent the app acts as.
The console's Approvals tab with a pending request
Requests that need a person wait here and on the phone.

FAQ

Where does the configuration live?

User scope by default (~/.claude.json); --scope project writes .mcp.json in the repository so a team shares it.

Can different projects use different agents?

Yes. Register Pink per project with a different agent key, or sign in and pick a different agent on Pink's page.

Official documentation

Menu names and settings paths follow each vendor's documentation at the verified date. If a vendor moves a menu, the linked page is the source of truth; the Pink side does not change.

Other clients