Payments for the agentic web,explained.

The loudest take on x402 is that demand isn't there, it's just crypto, and micropayments always fail. Some of that is fair. Here's an honest answer to each objection — including the one reason the old micropayment arguments don't apply when the buyer is software.

A user-agent string is free text — 'GPTBot' can be anyone. Web Bot Auth gives you cryptographic proof of which agent is really calling. Here's how verified identity works, and how it pairs with charging agents per request.

You built a useful MCP server. The market average price is $0. Here's how to choose a pricing model that isn't zero — per-call, subscription, or both — and how to handle the metering problems that make charging the genuinely hard part.

Three real ways to charge AI crawlers in 2026 — Cloudflare's Pay Per Crawl, marketplaces like TollBit, and the open x402 protocol. Here's how each one works, who it fits, and the trade-offs nobody puts in the launch post.

2026 gave us an alphabet soup of agent-payment standards — x402, AP2, ACP, MPP, plus L402. They sound like competitors. They're mostly layers. Here's the map: what each one does, where they overlap, and how to pick without guessing.

Blocking GPTBot and ClaudeBot is the default advice in 2026, and it's the option that leaves money on the table. Here's the third choice — charge crawlers per request at the edge — and when it beats both blocking and allowing.

Subscriptions and quotas were built for humans who plan ahead. Autonomous agents decide call-by-call. Here's why per-call pricing fits agent buyers — and when a subscription still wins.

A practical map of the ways to charge AI agents and crawlers — edge paywalls, pay-per-call APIs, MCP tool calls, paid data endpoints — and how they compare to API keys and card rails.

A step-by-step playbook for charging AI agents per API call: decide what to meter, set a price, drop in one SDK, test it for free, and go live — without building a billing system.

Most x402 writing is for API owners. This is for the other side — the developer building an agent that has to read a price, pay it, and continue. Here is what the wallet, the handshake, and the budget actually look like.

Stripe launched its Machine Payments Protocol in March 2026. x402 has been in production for longer. Here is how they actually differ — and which one fits which workload — without the marketing varnish.

MCP standardised how AI agents call your tools — but it left the bill unpaid. Here is how x402 fills that gap with a pay-per-call price on each tool, no API keys, no plans.

Programs are becoming first-class clients on the web. The piece that has been missing is a payments primitive software can read, decide on, and act on. Here is what 'signed 402' adds — and why it matters.

Pricing an API for autonomous AI callers is different from pricing for developers. Pick the right unit, anchor against three reference points, and use a test mode to iterate without burning real funds.

API keys plus monthly plans were built for human developers signing up. Autonomous AI agents want to pay per request and disappear. Here is how x402 differs — and where each still fits.

The end-to-end path for developers: register a monetised route, grab a test key, add one middleware, go live. Pick the official SDK for your stack — nine of them, one frozen contract.

Connect Cloudflare, write a pricing rule, and AI crawlers get quoted a price instead of taking your content for free — decided at the edge, before your origin, with humans untouched and no code changes.

How x402 works under the hood: the frozen X402v1 canonical string, HMAC-SHA256 request signing, the challenge/verify flow, fail-closed semantics, and byte-identical SDK conformance.

Plain-English explainer: x402 lets websites and APIs charge automated visitors (AI agents and crawlers) a small amount per request — no invoices, no crypto knowledge needed.