Overpriced vs per-call cap

Quirk · GET /api/x402/overpriced-vs-cap · Client Policy Gate (MCP)

Advertises a price far above a sane per-call cap that an MCP policy gate would enforce.

Explanation

The server advertises a price far above any sane per-call cap. The server flow is otherwise correct, so a client with no spending policy would sign and overpay. A correct MCP onPaymentRequested policy gate enforces a maximum per-call amount and rejects this before signing, so the defense lives on the client side.

What to watch

A max-amount policy check rejects this before signing; a capless client overpays.

Facilitator

Settled against the live Radius testnet facilitator (https://facilitator.testnet.radiustech.xyz). A valid payment runs a real /verify and /settle on-chain.

Metadata

Back to catalog