AgentPay x402 Facilitator
Server Details
Verify signed x402 payments; treasury-scoped settlement is irreversible.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: verify forwards an envelope for validation only, with no gas and no broadcast, while settle forwards an envelope for irreversible on-chain settlement. Their side effects and endpoints are different, so misselection is unlikely.
Both names follow the same pattern: x402_facilitator_<verb>. The naming is consistently snake_case and uses clear verbs, verify and settle.
Only two tools are exposed, which is minimal for a facilitator adapter and falls into the thin range. Each tool earns its place, but the set is narrow enough that it may feel under-scoped for broader facilitator use.
The core payment lifecycle is covered: verify checks validity and settlement authority, and settle performs the actual broadcast. Minor gaps may exist around discovery or supported-payment-method queries, but the essential operations are present.
Available Tools
2 toolsx402_facilitator_settleSettle an x402 payment on-chain (irreversible)ADestructiveInspect
IRREVERSIBLE SIDE EFFECT: forwards the envelope to POST https://x402-agent-pay.com/facilitator/settle. The existing facilitator first re-runs verify(), then refuses PAYEE_NOT_SERVED_HERE unless payTo is the AgentPay treasury (0x367F1b3D8Ca90D1e087481a9A40d585Bf3451a03 on Base / 6aCEuwH3PYx99cEmRz45otfxk39uF7ewGhqmvxfXisSG on Solana), then broadcasts via Coinbase CDP and returns a transaction hash. Malformed, unsigned, out-of-scope, or unverified payloads are rejected before any external transfer. This adapter never signs, never holds keys, and never bypasses those gates. Do not call this as a dry run.
Inputs: body (required). Returns: object
x402_facilitator_verifyVerify an x402 payment without moving fundsARead-onlyIdempotentInspect
Forward an x402 payment envelope to POST https://x402-agent-pay.com/facilitator/verify. Recovers the EIP-712 signer, checks payee/amount/expiry/nonce/USDC balance and spend authority. Free. No gas. No broadcast. Returns isValid plus invalidReason when the payload cannot clear. Authorization still lives in the existing facilitator implementation; this tool only forwards the JSON body.
Inputs: body (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read-only on-chain receipt check for x402 payments; confirm settlement before trusting a tx.
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Authorize x402 payments before signing with request-bound, signed safety decisions.
Verify and settle x402 stablecoin payments; browse the PayAI Bazaar of x402-payable resources.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables auditing x402 payment logs against delivery logs to issue signed proof-of-delivery receipts and verify payer spend health.-
- AlicenseAqualityBmaintenanceNon-custodial x402 payment checks: decode 402 responses, verify settlements against on-chain balance changes, lint scheme specs, and test facilitators.6Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to validate x402 endpoints and review on-chain payment evidence before relying on them, with free initial checks and automated USDC payments under configurable safety limits.35 PyPIMIT
- AlicenseAqualityBmaintenanceSeals each payment an AI agent makes (x402, Stripe, cards, etc) as a signed record with the company's own key: the agent declares the purchase before paying, checks it against its limits, and records the settlement after. Anyone can verify the records without relying on Luca.10Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.