# x402 isn’t good (yet) — Jan Curn, Apify

Source: [AI Engineer](https://www.youtube.com/watch?v=h6mi88VrPtQ)  
Feed7 permalink: https://feed7.dev/p/x402-isn-t-good-yet-jan-curn-apify-1mk89zm  
Published: 2026-09-01T19:00:09.000Z  
Trust: Source Linked (source_linked)

## Why Included

x402 servers can perform work before payment settlement, leaving a double-spend window. Builders should settle first or accept explicit counterparty risk until stronger schemes mature.

## Source Summary

In the described x402 flow, a server verifies a signed payment before blockchain settlement. A client can reuse the same funds to create **1,000 signatures**, leaving providers unpaid after doing work; x402 also expects **HTTP 402** where MCP authentication expects **HTTP 401**.

## Practical Implication

For work with meaningful marginal cost, settle before execution or reserve funds first. If pricing is variable, account for the extra latency, fees, and trust introduced by charging a maximum and refunding the remainder.

## Agent-Ready Context

In the described x402 flow, a server verifies a signed payment before blockchain settlement. A client can reuse the same funds to create **1,000 signatures**, leaving providers unpaid after doing work; x402 also expects **HTTP 402** where MCP authentication expects **HTTP 401**.

For work with meaningful marginal cost, settle before execution or reserve funds first. If pricing is variable, account for the extra latency, fees, and trust introduced by charging a maximum and refunding the remainder.

Coinbase's **batch settlement** escrows funds and signs micropayments off-chain, but Apify had not implemented it at the time of the talk. The ecosystem was described as early, with roughly **$1 million per month** in transaction volume.

## Connected Context

Feed7 judgment across 669 accumulated Signals:

This narrows payment-gateway optimism by identifying a settlement-order flaw beneath model policy and wallet budgets: valid signatures can authorize costly work without guaranteeing providers receive funds. It also exposes an x402–MCP status-code mismatch. Reservation, prior settlement, or explicit counterparty risk is therefore a protocol prerequisite, not an agent prompt improvement.

- [Agent Spending Without Controls — Rodrigo Coelho & Pranav Maheshwari, Edge & Node](https://feed7.dev/p/agent-spending-without-controls-rodrigo-coelho-pranav-maheshwari-edge-no-00wmfz6) — Its budgets and screening protect the buyer’s authorization boundary, while this Signal shows that those controls do not protect sellers from duplicated pre-settlement payment evidence.
- [When AI Agents Pay and Sellers Monetize: Building x402 Apps on AWS — Anil Nadiminti, AWS](https://feed7.dev/p/when-ai-agents-pay-and-sellers-monetize-building-x402-apps-on-aws-anil-n-1nj1n6a) — AWS’s deterministic wallet and edge controls can govern spend and meter access, but they do not resolve the separate requirement to reserve or settle funds before costly execution.
- [Why Your AI Agent Needs a Wallet: USDC and Nanopayments — Harshal Bhangale, Circle](https://feed7.dev/p/why-your-ai-agent-needs-a-wallet-usdc-and-nanopayments-harshal-bhangale-05ucp07) — Circle’s bounded wallet demonstrates useful purchasing authority, while the double-spend window narrows what a spending cap alone can establish about final settlement.
- [Security Firewall for Agents — Ryan Dahl, Deno](https://feed7.dev/p/security-firewall-for-agents-ryan-dahl-deno-12bkfg3) — Deno’s external proxy pattern offers a suitable enforcement point for protocol rules, but accepting verified signatures there would still be insufficient without settlement-aware execution.

## Context Map

- Layer: infra
- Domains: security
- Topics: agent-reliability, mcp, gateways

## Uncertainty

- Coinbase's **batch settlement** escrows funds and signs micropayments off-chain, but Apify had not implemented it at the time of the talk. The ecosystem was described as early, with roughly **$1 million per month** in transaction volume.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.