Pink Agentic AI Payments

com.pinkwalletPublished by pinkwallet.comOfficial publisherv0.1.3Updated Oct 30, 2026

Pink Agentic AI Payments: AI agents pay within spending rules (budgets, caps, approval). Sandbox.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an AI agent request vendor and invoice payments that Pink checks against spending rules, returning allow, human approval, or block.

What you can do
  • Check spending limits: remaining monthly budget, spent today, single-payment cap, vault balances and company daily ceiling
  • Review policy: list approved payees and the rules that apply to the agent, in evaluation order
  • Dry-run a payment to see whether it would be allowed, sent for approval or blocked, with the decision trace
  • Request a real payment and receive a single-use credential, a pending hold, or a block with the reason
  • Poll a pending hold for its credential once a person approves, and file receipts for completed payments
When to use it
Useful when an agent should be able to pay vendor invoices or top up API credits but only inside company spending rules, with caps, payee allow-lists and human approval above a threshold. The sandbox is meant for trying this out with test money before a production pilot.
Requirements
Either a remote Streamable HTTP endpoint or the local npm package run with npx (Node.js). A sandbox agent key in PINK_AGENT_API_KEY, obtainable without signup via the package's sandbox-creation flag or the sandbox API. Optional PINK_MCP_URL overrides the default sandbox endpoint. OAuth 2.1 with an Authorization header is also supported. Network access to Pink's servers.
Before you install
The agent can initiate real payment requests, which issue single-use payment credentials; the sandbox uses test money only, while the production pilot is a paid $99/month tenant that decides allow, block or ask and leaves actual payment to your own Stripe, card or bank. Treat PINK_AGENT_API_KEY and the Authorization header as secrets, and expect payment details to be sent to Pink's remote server.

Installation

In SourceWeft

  1. Open Pink Agentic AI Payments in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.pinkwallet%2Fagentic-payments-sandbox/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pink-agentic-ai-payments": {
      "type": "http",
      "url": "https://agentic-sandbox.pinkwallet.com/mcp"
    }
  }
}

README

Pink Agentic AI Payments MCP server: let Claude, ChatGPT or Cursor pay vendors and invoices within spending rules

pink-agentic-payments-mcp is the MCP server for Pink Agentic AI Payments (by PinkWallet). It lets an AI agent in Claude, ChatGPT, Cursor, VS Code, Windsurf or any other MCP client request a payment, such as paying a vendor invoice or topping up API credits, and Pink checks that payment against the company's spending rules (per-agent budgets, single-payment caps, payee allow-lists, human approval above a threshold) before any payment credential is issued. The agent never holds a standing card or key.

Production pilot: a private production tenant (decision-only: Pink decides allow, block or ask a person; your own Stripe, card or bank pays) is available for $99/month. In production, payments above an agent's per-payment limit wait for a person's approval. Details and checkout: https://pinkwallet.com/agentic/pilot/

Every payment request gets one of three answers: allowed (with a single-use credential), pending_human (a person is asked first), or blocked (with the reason).

Sandbox preview: test money only, no signup required to get a key.

Can Claude or ChatGPT pay an invoice through MCP?

Yes, with limits you set. Connect Pink as an MCP server, and the agent gets 7 payment tools (listed below). Asked to "pay the Acme invoice for $1,200", the agent calls pink.check_policy or pink.request_payment; Pink pays only if the invoice fits the rules, asks a person if it needs approval, or refuses and says why. Setup guides: Claude · ChatGPT (developer mode) · Cursor · Claude Code · Walkthrough: an MCP server that lets AI agents pay invoices.

How this package works

This package is a local stdio MCP server that bridges any MCP client to Pink's remote Streamable HTTP MCP server (https://agentic-sandbox.pinkwallet.com/mcp). It forwards tools/list and tools/call (and resources/prompts, if the remote adds them) transparently, so the local server always reflects whatever tools Pink's remote server currently exposes; nothing is hardcoded. Clients that support remote MCP can also connect to that URL directly.

Quick start

1. Get a free sandbox agent key

No signup needed. Either run:

bash
npx -y pink-agentic-payments-mcp --create-sandbox

which creates a sandbox workspace and prints a ready-to-paste client config, or create one yourself:

bash
curl -s -X POST https://agentic-sandbox.pinkwallet.com/v1/sandbox/workspaces

and take any agents[].key from the response.

2. Add it to your MCP client

Claude Desktop (claude_desktop_config.json), Cursor, Windsurf, and most other stdio-based MCP clients:

json
{  "mcpServers": {    "pink": {      "command": "npx",      "args": ["-y", "pink-agentic-payments-mcp"],      "env": { "PINK_AGENT_API_KEY": "pk_sandbox_agent_..." }    }  }}

VS Code (.vscode/mcp.json):

json
{  "servers": {    "pink": {      "command": "npx",      "args": ["-y", "pink-agentic-payments-mcp"],      "env": { "PINK_AGENT_API_KEY": "${input:pink_agent_key}" }    }  }}

Env vars:

  • PINK_AGENT_API_KEY (required) — your agent key from a sandbox workspace.
  • PINK_MCP_URL (optional) — defaults to https://agentic-sandbox.pinkwallet.com/mcp.

Tools

These are live from the remote server's tools/list response (see TEST-OUTPUT.txt for the full run):

ToolWhat it does
pink.get_budgetWhat this agent may still spend: monthly budget left, spent today, single-payment cap, vault balances, company daily ceiling.
pink.list_payeesSuppliers, platforms and contractors this company has approved. Paying anyone else stops and asks a person.
pink.list_rulesThe policy rules that apply to this agent, in evaluation order. First match decides: allow, ask, or block.
pink.check_policyDry run. Returns would_allow / would_ask / would_block with the rule and full decision trace. Nothing is spent or held.
pink.request_paymentThe real call. Returns allowed with a single-use credential, pending_human with a hold_id while a person is asked, or blocked with the reason.
pink.get_credentialPoll a pending hold. Once a person approves, this returns the credential.
pink.report_receiptFile the receipt for a completed payment so it reconciles.

How this was tested

TEST-OUTPUT.txt in this repo is the full, unedited output of three real runs against a live sandbox workspace (test money only):

  1. The built server (dist/bin.js) driven over stdio by an MCP SDK test client — tools/list plus pink.request_payment calls that returned real allowed (with an issued sandbox credential), blocked (over monthly budget), and pending_human (new-payee approval) decisions.
  2. The official MCP Inspector CLI (npx @modelcontextprotocol/inspector --cli) run headless against the same built server.
  3. The same stdio test run again from a packed tarball (npm pack then npx -y ./pink-agentic-payments-mcp-0.1.0.tgz) in a clean directory, to prove the npx install path works end to end.

Links

Status

Sandbox preview (test money only). Published on npm as pink-agentic-payments-mcp — npx -y pink-agentic-payments-mcp is all you need, no clone or build step required.

License

MIT

Source: README.md at commit 7e96361

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.1.3LatestOct 15, 2026
  2. v0.1.2Oct 13, 2026
  3. v0.1.1Oct 5, 2026
  4. v0.1.0Oct 1, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts