Join early accessPink Agentic AI Payments (by PinkWallet, early access) is the approval layer between AI agents and company money: plain-language rules, per-agent budgets and human approvals decide each payment before a single-use card or bank transfer is issued. Pick the integration path that matches your agent's stack below.
Connect via MCP
For agents already running on an MCP-capable client or framework — Claude, Cursor, VS Code, the OpenAI Agents SDK, LangChain — connect directly with no custom HTTP client to write.
| Tool | What it does |
|---|---|
pink.get_budget | Check the calling agent's remaining monthly budget and per-payment cap |
pink.list_payees | List the payees this agent is allowed to pay |
pink.list_rules | List the policy rules that apply to this agent |
pink.check_policy | Dry-run a payment against the rules without submitting it |
pink.request_payment | Request a payment; the rules decide ALLOW, ASK A PERSON, or BLOCK |
pink.get_credential | Retrieve the single-use card or bank-transfer credential once approved |
pink.report_receipt | File the receipt for a completed payment |
Connect via REST
For any language or agent framework without native MCP support, call the REST API directly.
| Method | Endpoint | What it does |
|---|---|---|
POST | /v1/payments/check | Dry run: would-allow / would-ask / would-block with the full rule trace |
POST | /v1/payments | Request a payment |
GET | /v1/payments/{id} | Poll a pending payment; returns the credential once approved |
POST | /v1/payments/{id}/receipt | File the receipt for a completed payment |
Sandbox live: test credentials only, no money moves.Create a free sandbox workspace — no signup form needed. Production is not yet available.
Use MCP if your agent already runs on an MCP-capable client or framework (Claude, Cursor, VS Code, the OpenAI Agents SDK, LangChain) — you get 7 tools (get_budget, list_payees, list_rules, check_policy, request_payment, get_credential, report_receipt) with no custom HTTP client to write. Use REST if your agent framework doesn't speak MCP, or you want direct control over the HTTP calls; both paths run against the same policy engine and sandbox workspace.
Call POST /v1/payments/check (REST) or pink.check_policy (MCP) first — it's a dry run that returns would_allow, would_ask, or would_block along with the full rule trace, without creating a real payment request.
POST /v1/payments returns one of three states: 201 if the rules allow it immediately, 202 if it's pending human approval, or 403 if it's blocked. For a pending request, you poll GET /v1/payments/{id} until it resolves, which returns the credential once approved. Sending an Idempotency-Key header makes retries of the same request safe.
No. The sandbox is live: create a free sandbox workspace at https://agentic-sandbox.pinkwallet.com/ (test credentials only, no money moves). Production is not yet available.
Contact Email: [email protected]
ALTIVOX SPHERE SPÓŁKA ZO.O. is a wholly owned subsidiary of PinkWallet, registered in Poland in the Polish Ministry of Finance's virtual-currency activity register (registration number: RDWW-1797), authorized to provide cryptocurrency exchange and digital asset custody services in the EU under AML/CTF regulations.
PinkWallet (Pink Technologies Inc) is registered as a Money Services Business with the U.S. Department of the Treasury, FinCEN (Registration No. 31000321450011), enabling it to provide users with cross-border fund settlement and international payment services under the U.S. regulatory framework.
PinkWallet (Pink Wallet Technology Inc.) is registered as a Money Services Business with FINTRAC, Canada's financial intelligence unit (Registration No. C100001073), enabling it to provide users with cross-border fund settlement and virtual currency services under the Canadian regulatory framework.
