● Agentic Commerce on Cloudflare

Cloudflare · Agentic Commerce

AI agents are starting to buy
on behalf of real users.

ChatGPT, Perplexity, Claude and other agents can now browse real merchant sites and make purchases on behalf of authenticated consumers. Cloudflare is building the tools to make that work — agent identity, cryptographic verification at the edge, and integrations with payment schemes like Visa's Intelligent Commerce.

Pick your lane. Each one covers what you need to build, who handles what, and where to go next.

Ready today

I'm building an agent

You're building an AI agent that shops, books, or transacts on behalf of users. Cloudflare's Agents SDK, Workers AI, AI Gateway, Browser Rendering and more give you the full runtime — plus TAP signing primitives to get your agent recognised by merchants.

See the stack →

Ready today

I run a merchant

You want to accept agent traffic on your site without getting scraped. You need to tell real agents from bots cryptographically, at the edge. Cloudflare has shipped tooling for this part — starting with TAPKit.

Start here →

Early

Something else

Payment scheme, issuer, processor, analyst, or just curious? The full agentic-commerce stack involves a lot more than merchants and agents. Tell us what you're working on — we want to hear from you.

Get in touch →

What's actually happening

A short map of the space, so you know where you are. Cloudflare sits at the merchant's edge; the rest of the stack is coordinated with payment schemes and agent platforms.

Agents authenticate themselves

Agents sign every request with an RFC 9421 HTTP Message Signature, identifying themselves to merchants. Visa's Trusted Agent Protocol (TAP) is the current standard; others will follow.

Users stay in control

Card enrolment, passkeys, and per-transaction approval happen in the agent's own UI, with the card network enforcing controls at the network level (merchant + amount match).

Merchants verify at the edge

Cloudflare's edge checks the agent's signature against published public keys before traffic ever reaches the merchant's origin. A legitimate agent gets through. A scraper gets blocked.

Payment rails stay normal

From the merchant's processor forwards, it's a regular card transaction with a tokenised PAN. Nothing about the settlement flow changes.

Why Cloudflare.

Several reasons agentic commerce lands on our platform naturally, and a couple of specific investments we've already made.

We co-developed TAP with Visa

Visa's Trusted Agent Protocol was designed with Cloudflare's Web Bot Auth as the canonical verification layer. Our implementation isn't a port — it's a reference.

We're already the merchant's edge

A huge slice of real merchant traffic already terminates at Cloudflare. That means merchants don't need a new network path, a new vendor, or a new trust boundary to start accepting agent traffic — they get it at the edge they already run.

The agent runtime ships today

Cloudflare Agents SDK, Workers AI, AI Gateway, Browser Rendering, Workflows and Vectorize compose into a real agent runtime right now. Three commands to a deployed agent. That's not promised — it's in production.

Bot management and trusted-agent auth together

Distinguishing real agents from malicious scrapers is exactly the problem Cloudflare's bot-management already solves at scale. Trusted-agent auth is a natural extension, not a parallel system.