{ "video": { "id": "h6mi88VrPtQ", "title": "x402 isn’t good (yet) — Jan Curn, Apify", "duration": 1248, "upload_date": null, "channel": "AI Engineer", "source": "AI Engineer" }, "analysis": { "video_id": "h6mi88VrPtQ", "title": "x402 isn’t good (yet) — Jan Curn, Apify", "one_liner": "Apify's CEO, two days after 10x-ing the x402 tool market by putting 20,000 Apify actors on it, walks through exactly where x402 still breaks: client-side double-spending, a 402-vs-401 collision with MCP auth, and no working metered billing — and shows the prepaid-token workaround (agi.apify.com) they shipped instead.", "summary": "Jan Curn deliberately echoes David Cramer's 'MCP isn't good yet' talk from last year's AI Engineer World's Fair — MCP went on to win, and he expects the same arc for x402. He argues crypto is genuinely the right substrate for agentic payments (microtransactions are impossible on cards, and with no agent identity you cannot allow chargebacks, so payments must be one-way), then details three concrete protocol defects Apify hit while shipping its Coinbase x402 integration: nothing stops a client double-spending the same wallet before settlement, x402's mandatory HTTP 402 first response collides with MCP auth's mandatory 401, and the long-awaited 'up to' scheme still doesn't fix double-spending. Apify's answer was to stop bending its API and instead publish agi.apify.com — an 'agent general interface', a single ugly markdown page telling agents how to buy a prepaid Apify token — while it waits on Coinbase's new batch-settlement scheme.", "key_points": [ "Apify runs ~45,000 AI tools ('actors'), with the community earning over $1 million/month in payouts; its x402 launch with Coinbase two days earlier added 20,000 tools to a market that previously had ~2,000, roughly 10x-ing the agentic tool market, and got about 1 million views.", "The agentic payments field is a crowded battleground: L402, MasterCard Agent Pay, x402 (Coinbase), Kite Pay from Skyfire with Visa, AP2 by Google, ACP by OpenAI and Stripe, Tab by Visa, UCP by Google and Shopify, ACTP by Alipay, MPP by Stripe and Tempo, AMP by Alipay, UnionPay's, APP by OKX, and Agent Pay for Machines by MasterCard.", "Of the two leading crypto options, x402 is ~20x larger than Stripe's MPP in both transaction count and volume (checked the day before the talk), which is why Apify implemented x402 first and MPP second.", "Double-spending is the core defect: between the facilitator verifying a signature and the transaction actually hitting the blockchain, the client can reuse the same wallet and money — it could mint 1,000 signatures against 1,000 requests. Fine for zero-marginal-cost API calls, but ruinous when the work is non-trivial or you pay an external service. The only fix is to do the work *after* settlement.", "Protocol collision: x402's spec mandates HTTP 402 as the server's first response, while MCP auth mandates 401, and you can't return both. Companies work around it with duplicate hosts (x402.alchemy.com, mcp.alchemy.com, mpp.alchemy.com) — Curn calls this an anti-pattern, 'like 20 different Amazons' for different credit cards, and argues the payment challenge should be expressible in a header alone.", "Metered billing is still unsolved: 'exact' (fixed fee per call) shipped May 2025; v2 was announced December 2025 promising the 'up to' scheme, which took nearly another half year to land (2–3 months before the talk) — and 'up to' turned out to inherit the same double-spend hole. Apify's stopgap is charge-fixed-then-refund-the-remainder, which costs two blockchain transactions, extra fees and settlement time, and requires the client to trust the server to refund.", "Coinbase's batch settlement scheme, introduced ~2 months before the talk, looks promising: deposit into an EVM escrow, receive a cryptographic voucher, sign off-chain micropayments against it, settle in batch, then release the escrow. Apify is implementing it now and hasn't shipped it.", "Apify's shipped solution is agi.apify.com — 'agent general interface', not artificial general intelligence — a single markdown page of instructions for agents, deliberately not designed for humans so it can be iterated on freely, unlike the API that tens of thousands of customers depend on. An agent pays $5 via x402 or MPP, gets a prepaid Apify token back, and uses it through the normal API or MCP. No skill or client integration required.", "The ecosystem is so immature that Apify had to build its own local wallet tool (generate a local key, fund it, show a QR code); total x402 volume is around $1 million/month, which Curn calls 'nothing'. The live demo failed on stage." ], "takeaways": [ "Never hand over the goods before settlement on x402 — do the work only after the facilitator settles, or you're exposed to a client that spends the same wallet balance across many concurrent requests.", "Don't duplicate your API host per payment protocol (x402.yourco.com, mpp.yourco.com). Consider Apify's route instead: a single agent-facing markdown endpoint that sells a prepaid token, keeping your stable API and MCP surface untouched.", "If your billing is metered rather than fixed-fee, expect to hand-roll it — 'exact' plus a refund of the unused remainder works but costs two on-chain transactions, and 'up to' does not remove the double-spend risk. Watch batch settlement as the real fix.", "Just try it: Curn only tried x402 himself a few weeks before the talk after assuming the crypto jargon made it hard, and says you can be up and running in about 10 minutes.", "Plan for the end of token subsidies — when agents pay real token costs, build-vs-buy tips toward buying external services, which is when agentic payment volume ramps." ], "topics": [ "agentic-payments", "x402", "crypto", "mcp", "agentic-commerce", "protocols", "micropayments", "marketplaces" ], "tools": [ "Apify", "x402", "Coinbase", "MPP (Stripe machine payments protocol)", "MCP", "Sentry MCP", "Claude", "ChatGPT", "Stripe", "Tempo", "Visa", "MasterCard Agent Pay", "Skyfire", "Google AP2", "OpenAI ACP", "Shopify UCP", "Alipay ACTP / AMP", "OKX APP", "UnionPay", "L402", "agi.apify.com", "Alchemy" ], "quotes": [ { "text": "Basically, there is like nothing preventing the the client from double spending.", "at": "09:59", "url": "https://www.youtube.com/watch?v=h6mi88VrPtQ&t=599s" }, { "text": "Why would you have to duplicate like your API host for different payment providers? It's like imagine like you had to like amazon.com for different like credit cards. You had like 20 different Amazons.", "at": "11:44", "url": "https://www.youtube.com/watch?v=h6mi88VrPtQ&t=704s" }, { "text": "why would we need to do these workarounds, you know? This protocol should support these things out of the box.", "at": "14:35", "url": "https://www.youtube.com/watch?v=h6mi88VrPtQ&t=875s" }, { "text": "I think there's like $1 million transaction volume like per month. Like this is nothing, right? Like the economy is much much bigger.", "at": "19:37", "url": "https://www.youtube.com/watch?v=h6mi88VrPtQ&t=1177s" } ], "words": 4436 }, "summary_url": "/#h6mi88VrPtQ", "transcript": { "html": "/transcripts/h6mi88VrPtQ.html", "txt": "/transcripts/h6mi88VrPtQ.txt", "vtt": "/transcripts/h6mi88VrPtQ.vtt" } }