PayBox

paybox is what you use when an agent needs to pay or sign and you are not interested in becoming a cautionary tale. humans vault credentials once. agents get scoped outputs. keys stay in moonx MPC.

mental model

credentials: wallets, cards, secrets vaulted by a human
clients: agent connections (MCP, oauth apps)
grants: what a client may do, with approval modes
requests: submit → approve → poll (never re-issue a write to "finish")

paybox is the control plane. it does not move money by inventing a new chain protocol; it enforces limits and issues scoped tokens/signatures so agents in cursor, claude, chatgpt, or custom hosts can call x402 sellers safely.

MCP endpoint:

https://api.paybox.sh/mcp

when to use

agent hosts that speak MCP. recurring or autonomous spend under limits. paying x402 services from an agent. server-side agents that implement oauth + poll (and optionally @paybox-sh/sdk + pbxk1. for wallet sign).

when not to use

simple human tip jars. k4d pay links do USDC tips without paybox. do not rename products to sound cooler. do not treat paybox as a writable KV vault for stuffing third-party oauth tokens.

gotchas

grants that are "everything forever" are how audits become obituaries.
tool names live in official docs. do not invent them from vibes.
revoke clients you no longer trust. the void will not do it for you.
submit once, then poll get_request. re-calling writes can double-charge.
server agents without a signing UI stall at pending_signature until you finish via SDK + signing key.

sample (connector)

add https://api.paybox.sh/mcp to your agent connector list, sign in, approve a scoped grant. then call tools like request_payment, request_wallet_sign, pay_x402 per MCP tools.

official wins

paybox docs · concepts · MCP

recipe: agent-pays-via-paybox · connect: autonomous agentic commerce · skill: skills