Coinbase, Block, Cloudflare: The Other Agent Payment Builders (And Their Shared Gap)

Q: What is Cloudflare building for agent payments?

Cloudflare's play is infrastructure-layer simplicity. Its Agents SDK lets developers deploy AI agents on Cloudflare Workers with built-in state management, tool-calling, and MCP support. Cloudflare positioned itself early as the hosting layer for MCP servers. Agents built on its platform can access payment, calendar, email, and dozens of other tools through a standard interface.

_Last updated: 2026-06-10_

Beyond Stripe, three companies are actively building production agent payment infrastructure: Coinbase (x402 protocol and AgentKit), Block (MCP integrations and co-founding the Agentic AI Foundation), and Cloudflare (Agents SDK with built-in MCP support). Each attacks the problem from a different angle. None of them centralizes cross-rail policy, approval workflows, or audit trails. That's where a dedicated control plane fits alongside them.

Key takeaways

Coinbase leads on on-chain agent payments via x402 and AgentKit; Block is integrating agent commerce into its merchant and developer tools; Cloudflare is making agent deployment and payments infrastructure-layer simple
All three rely on MCP (Model Context Protocol) as the interface standard, the protocol Anthropic donated to the Linux Foundation in December 2025
On-chain approaches (Coinbase, partly Block) and card approaches (Cloudflare, Stripe) serve different agent use cases and aren't direct substitutes
The shared gap across all three: none provides a cross-rail policy engine, human approval workflows, or an immutable audit trail that sits above the payment rail
A control plane like Shatale is designed to complement these builders, not replace them. It governs what agents are allowed to do, regardless of which rail they use

---

What is Coinbase building for agent payments?

Coinbase has two active agent payment products: x402, the open payment standard Coinbase created (now governed under the Linux Foundation), and AgentKit.

x402 is an HTTP-native micropayment protocol built on stablecoins (primarily USDC on Base, Coinbase's L2 chain). The name references HTTP 402, the "Payment Required" status code reserved in the original HTTP spec but never implemented. x402 lets an agent pay for an API call in a single HTTP round-trip, with payment encoded in the response headers. For agents making many small, repeated payments (paying per inference call, buying access to metered tools) it removes the friction of traditional card flows entirely.

AgentKit is Coinbase's developer SDK for agent wallets. It wraps wallet creation, transaction signing, and the x402 flow into Python and TypeScript primitives agents can call directly. In early 2025, Coinbase extended AgentKit with an MCP server, so agents can access wallet and payment actions through the same interface they use for everything else.

What x402 doesn't include is any layer for your finance team, no policy capping this agent at $500/day on approved vendors, no approval queue when that threshold approaches, no audit log formatted for a controller.

---

What is Block building for agent payments?

Block, parent of Square, Cash App, and Spiral (formerly Square Crypto), is taking a broader infrastructure play.

In December 2025, Block co-founded the Agentic AI Foundation alongside Anthropic and OpenAI, under the Linux Foundation. The foundation's mandate is open, vendor-neutral development of agentic AI standards and tooling. Its anchor projects are MCP (from Anthropic), goose (from Block), and AGENTS.md (from OpenAI). Block's position is distinctive: it sits on both sides of commerce (Square for merchants, Cash App for consumers) and has deep experience with the payment flows agents will eventually replicate at scale.

On the developer side, Block has released MCP integrations that expose Square's payment and commerce APIs to agent frameworks. An agent using an MCP-compatible host can query Square's catalog, initiate a payment, or check order status through the same tool-call interface it uses for everything else.

The gap is governance. Block's MCP integrations are developer tooling. No policy enforcement layer, no approval workflow, no cross-rail visibility for the companies deploying those agents.

---

What is Cloudflare building for agent payments?

Cloudflare's play is infrastructure-layer simplicity. Its Agents SDK lets developers deploy AI agents on Cloudflare Workers with built-in state management, tool-calling, and MCP support. Cloudflare positioned itself early as the hosting layer for MCP servers. Agents built on its platform can access payment, calendar, email, and dozens of other tools through a standard interface.

On payments, Cloudflare has partnered with providers (including Stripe) to make card-based flows accessible through agent tool calls. Deploy an agent, connect it to an MCP payment server, and it can transact without building the payment integration from scratch.

The tradeoff is what you'd expect from a platform play: infrastructure, not governance. Policy, approvals, and audit are your problem.

---

On-chain vs. card: are these actually substitutes?

Not really. They serve different use cases.

| Dimension | On-chain (x402, stablecoins) | Card-based (Stripe Issuing, Cloudflare integrations) |

|---|---|---|

| Payment size | Micropayments ($0.001–$10 typical) | Any size; better for larger B2B spend |

| Settlement speed | Near-instant, on-chain | 1-3 business days net settlement |

| Merchant acceptance | Protocol-aware endpoints only | Any merchant that accepts cards (100M+) |

| Compliance surface | Crypto regulatory requirements | Traditional card network compliance |

| Developer experience | Requires wallet/key management | Standard card API patterns |

| Audit trail | On-chain ledger (public, but hard to interpret) | Issuer logs + processor records |

An agent that pays for API calls will likely use x402. An agent that books business travel, renews SaaS, or procures physical goods will likely use a card. A production fleet probably needs both. That's exactly why cross-rail governance matters.

---

What none of them centralize

Each of these builders has a clear strength: Coinbase in on-chain protocol, Block in merchant-side reach, Cloudflare in deployment simplicity.

None of them is building the layer that sits above the rails and answers: is this agent allowed to make this purchase, right now, under current policy, with the right approvals in place?

That's the control plane. It's the difference between having payment rails and having governed spending. For what the control plane actually needs to include, and why the money plane and control plane are separate jobs, [the comparison of agent payment infrastructure options](/blog/best-payment-infrastructure-ai-agents) covers the full decision framework.

Shatale's four pillars, agent-scoped virtual cards, real-time policy enforcement at the authorization moment, human approval workflows, and immutable audit trails, are designed to sit alongside any of these rails, not replace them. An agent spending via x402 and an agent spending via a Stripe-issued card can both run under the same policy engine.

---

Frequently asked questions

What is x402 and how does it work for AI agent payments?

x402 is an HTTP-native micropayment protocol that uses the reserved HTTP 402 status code to trigger payment. When an agent requests a resource, the server responds with payment instructions; the agent pays (typically in USDC on Base) and retries the request. It's designed for high-frequency, small-value, machine-to-machine payments without a checkout flow.

Is Block's Agentic AI Foundation the same as Anthropic's MCP standard?

Related but distinct. MCP (Model Context Protocol) is a tool-interface standard Anthropic donated to the Linux Foundation in December 2025. It defines how agents communicate with tools. The Agentic AI Foundation is the vendor-neutral home for open agentic AI projects under the Linux Foundation, and MCP is one of its anchor projects, alongside Block's goose and OpenAI's AGENTS.md. It is not a payments or commerce-standards body.

Does Cloudflare's Agents SDK include payment controls or just payment access?

Payment access only. Cloudflare's SDK makes it easy to connect an agent to a payment MCP server, but it doesn't enforce spend policies, route approvals to humans, or maintain audit trails. That layer is the developer's (or a control plane's) responsibility.

Can an AI agent use both on-chain and card payment methods?

Yes, and production fleets often will. On-chain rails (x402, stablecoins) are better for micropayments to protocol-aware endpoints. Card rails cover the vast majority of commercial vendors. A well-governed agent fleet needs a control plane that can enforce consistent policy across both.

Where does Shatale fit relative to Coinbase, Block, and Cloudflare?

Shatale is a control plane, not a payment rail. It sits above whichever rails your agents use and enforces policy, routes approvals, and writes immutable audit logs at the authorization moment. It complements Coinbase, Block, and Cloudflare rather than competing with them.

---

For the full framework on evaluating agent payment infrastructure, including what to look for beyond individual rails, read [choosing the best payment infrastructure for AI agents](/blog/best-payment-infrastructure-ai-agents).