# As a condition of accessing this website, you agree to abide by the following # content signals: # (a) If a Content-Signal = yes, you may collect content for the corresponding # use. # (b) If a Content-Signal = no, you may not collect content for the # corresponding use. # (c) If the website operator does not include a Content-Signal for a # corresponding use, the website operator neither grants nor restricts # permission via Content-Signal with respect to the corresponding use. # The content signals and their meanings are: # search: building a search index and providing search results (e.g., returning # hyperlinks and short excerpts from your website's contents). Search does not # include providing AI-generated search summaries. # ai-input: inputting content into one or more AI models (e.g., retrieval # augmented generation, grounding, or other real-time taking of content for # generative AI search answers). # ai-train: training or fine-tuning AI models. # ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF # RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT # AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET. # BEGIN Cloudflare Managed content User-agent: * Content-Signal: search=yes,ai-train=no Allow: / User-agent: Amazonbot Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: CloudflareBrowserRenderingCrawler Disallow: / User-agent: Google-Extended Disallow: / User-agent: GPTBot Disallow: / User-agent: meta-externalagent Disallow: / # END Cloudflare Managed Content
Protocol deep dives, MCP server walkthroughs, and weekly x402 on-chain metrics — for developers building the infrastructure that lets agents pay, earn, and transact.
Why now
Seven competing standards — x402, ACP, UCP, A2A, TAP, AdCP, ARTF — are fighting to become the settlement layer for trillions in agent-initiated transactions. No newsletter tracks this with the technical rigor builders actually need.
What we cover
Weekly status on x402 vs ACP vs UCP vs TAP — adoption metrics, interoperability gaps, and who's winning the standard war.
Step-by-step guides to deploy paid MCP servers, integrate x402 into your agent, and earn USDC with real transaction data included.
Weekly x402 transaction volumes, active wallets, and stablecoin flows pulled from Dune Analytics — raw data, real insight.
Everyone covers the buyer side. We cover merchant acceptance infrastructure — the missing half of agentic payments nobody else writes about.
Vulnerability tracking, CVE coverage, and practical hardening guides for MCP deployments at production scale.
EFTA, TILA, and emerging frameworks for agent-initiated transactions — translated for builders, not lawyers.
Sample issue
Every issue is technically dense, practically useful, and built for the people shipping this stack.
Seven protocols launched in twelve months. AWS, Coinbase, Stripe, OpenAI, Visa, and Cloudflare all shipped competing infrastructure for agent-to-agent payments in 2025–2026. Here's what each one actually does — and who's ahead.
When Coinbase and Cloudflare published the x402 specification in September 2025, they bet that HTTP's native status code — 402 Payment Required — was the right primitive for machine-to-machine payments. Agents already speak HTTP. Don't build a new protocol; extend the existing one.
Within 30 days, x402 transactions spiked 10,780% on Base. By April 2026, the Linux Foundation launched the x402 Foundation with 20+ members including AWS, Stripe, Google, Visa, and Mastercard...
Subscribe
The weekly digest, delivered to your inbox. No credit card. No catch.
About
Agent Commerce Weekly covers the protocols, standards, and infrastructure powering autonomous commerce. Protocol deep dives, builder walkthroughs, weekly on-chain metrics, and regulatory tracking. No market commentary. No price takes. The technical layer, weekly.