SafePayevery payment, sealed
session … PayPal sandbox
Layers Nemotron reasoning: on Tavily web verify: on Agent Toolkit gate: on state: durable (Supabase) Telegram approvals: on operator actions: open (demo)
Connect an agent

Any agent asks SafePay before it pays.

Agents now pay through their own checkout: Meta's Muse checks out with PayPal, Shop Pay and Stripe Link; others use ACP or the PayPal Agent Toolkit. SafePay does not need to hold the money to protect it. Connect SafePay Check as a remote MCP server: before any payment the agent asks, SafePay judges it with the same guardrail as every payment here (policy, payee history, a live web check of the merchant, an intent check against the task), chains the verdict and returns a signed attestation the merchant can verify. No tool in this connector moves money.

Endpoint

https://safepay.agentposhq.com/mcp

Listed in the official MCP Registry as com.agentposhq.safepay/check.

MCP over streamable HTTP (stateless, JSON responses). Auth: Authorization: Bearer spk_…, an agent key. The key names your account: you see only your own policy and checks, and the policy you set in the console for this session is the one your agent is judged under. Once the key exists the session is an account: only a change signed with your console's operator key, or a request carrying the connector key, can alter its rules, and nobody can issue a replacement key without presenting the current one.

Tools

safepay_check_paymentrecords a check, moves no money

Before checkout: merchant, amount, task; in dollars or in PYUSD or USDC with its network and wallet address. Answers allow, hold or block with reasons, a check id and a signed precheck attestation valid for 15 minutes. The log keeps only hashes of the payee and the task.

safepay_verifyread only

Verifies a seal id, a seal receipt or a precheck attestation against the published Ed25519 key.

safepay_verify_settlementread only

For a stablecoin payment: reads the Stellar transaction from the public ledger and checks it against the precheck (succeeded, approved payee, Circle's USDC, no more than approved, while the check was valid). Returns a signed result.

safepay_policyread only

The rules this key is judged under, in plain words, with their fingerprint.

safepay_recent_checksread only

This account's latest checks: verdict, merchant, amount, when.

Meta Muse

Muse can build a connector to a hosted MCP server from a message. Send it this, then enter the key when Muse asks for it through its credential prompt (never paste a key into the chat):

Connect to the SafePay Check MCP server at https://safepay.agentposhq.com/mcp
(streamable HTTP, auth: Authorization: Bearer header). Test every tool, then save
it as a skill. From now on, before any purchase or payment, call
safepay_check_payment with the merchant, the total and my request. If the verdict
is allow, continue to checkout; if hold, show me the reasons and ask me; if block,
do not pay and tell me why.

Muse Code (terminal agent): add a streamable HTTP server named safepay with this URL and the Authorization header to the mcpServers block of ~/.config/muse/settings.json, following the field names in the Muse Code documentation.

SafePay Check was submitted to Meta's Muse Connector Platform on November 7, 2026 and is under review; it is not a listed Muse connector yet. Muse availability depends on your region.

Claude, Cursor and any MCP client

claude mcp add --transport http safepay https://safepay.agentposhq.com/mcp \
  --header "Authorization: Bearer spk_your_key"

Or by hand, the same JSON-RPC any MCP client sends:

curl -s https://safepay.agentposhq.com/mcp -H "Content-Type: application/json" \
  -H "Authorization: Bearer spk_your_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"safepay_check_payment",
       "arguments":{"merchant_name":"Notion","amount":48,"merchant_url":"https://www.notion.so",
                    "task":"Pay our monthly software invoices"}}}'

What a check proves

That this payment was judged before it was made, under your rules, and what the verdict was. The attestation is signed with SafePay's published key (/.well-known/safepay-seal-keys.json), names the payee by domain and a hash of its address, and points at the link in the hash chain where the check is recorded.

What it does not do

It does not pay, refund or move money, and it does not see card or bank credentials. The agent's own checkout moves the money. A verdict is advice the agent is told to follow; for payments SafePay releases itself, use the full API and the seal. Data handling: privacy · terms · security.