Agentic Commerce Web Bot Auth

Identity Tells You Who.
It Doesn't Tell You What They're Doing.

Google's Universal Commerce Protocol opens your checkout to AI agents. Identity verification tells you it's Gemini. It doesn't tell you Gemini is enumerating your catalog.

Talk to Us Read the Technical Deep-Dive

Three Layers of Agentic Commerce Security

UCP isn't a standalone security solution. It's one layer of a protection stack.

Layer 1

UCP Protocol

The Handshake

Standardizes how agents and merchants communicate. Checkout sessions, OAuth identity linking, embedded checkout.

Provided by: Google, Shopify

Layer 2

Agent Identity

The ID Card

Cryptographic agent verification. Proves an agent is who it says it is, and catches whatever is only claiming to be.

Built on: Web Bot Auth (HTTP Message Signatures). WebDecoy verifies it.

Layer 3

Behavior

What the Agent Does

A verified identity says nothing about intent. This layer watches what the client actually touches, over time and across IP addresses.

WebDecoy today: decoys, JA4 and actor identity

Agent identity, on any traffic

WebDecoy verifies agent identity with Web Bot Auth (RFC 9421), the HTTP Message Signatures primitive agentic-commerce protocols are converging on. It runs on any traffic WebDecoy sees, not only inside a UCP checkout session. Adoption is still early: most automated traffic carries no signature yet, so treat signature verification as the layer that strengthens as operators adopt it.

The Problem

Verified Agents Can Still Attack

Identity verification proves who. It doesn't monitor intent. A verified agent can still:

  • Enumerate your catalog

    Create sessions for every SKU to extract real-time pricing and availability

  • Hold your inventory

    500 verified sessions during a limited drop = effective DoS

  • Test stolen cards

    Identity verification doesn't prevent payment fraud attempts

  • Harvest shipping rates

    41,000 zip codes x 50,000 SKUs = 2 billion data points

Catalog Enumeration Attack (illustrative)
# Verified agent, malicious intent
for product_id in catalog:
    session = create_checkout_session({
        "line_items": [{
            "item": {"id": product_id},
            "quantity": 1
        }]
    })

    # Extract pricing data
    pricing[product_id] = {
        "price": session["totals"]["subtotal"],
        "available": session["status"] != "unavailable"
    }

    # Never complete - just harvest
    # Identity check sees: "Verified agent"
    # It does not see: the pattern

What WebDecoy Provides Today

These are shipping features that apply to agent traffic now, inside or outside a UCP checkout.

Signed Agent Verification

Verifies Web Bot Auth signatures (RFC 9421 HTTP Message Signatures) against the operator’s published keys. Crawlers that don’t sign are checked against published IP ranges with forward-confirmed reverse DNS.

Web Bot Auth IP range + rDNS

Impersonation Detection

A request that claims a verifiable identity and fails the check is scored as agent impersonation: tripwire grade, the same weight as a honeypot hit. Agents that simply don’t sign yet stay “claimed”, never accused.

Forged identities Claimed vs. verified

API and Endpoint Decoys

Fake API endpoints at paths you choose. They accept GET, POST, PUT, PATCH and DELETE, capture the request body, and flag attack patterns. No real shopper or legitimate integration has a reason to call them.

Endpoint decoys Body capture

JA4 TLS Fingerprinting

Where WebDecoy sees the TLS handshake, the JA4 fingerprint reveals the client stack behind the user agent, for example a Python script claiming to be a browser.

JA4 JA3

Actor Identity Across IPs

Detections resolve to a persistent actor, so a client rotating through many IP addresses is still recognized as one actor, with the evidence attached.

Cross-IP actors Evidence trail

Shopify Order Flags

The Shopify app links orders to the actor behind them and flags risky ones in your admin, with the evidence. It never cancels an order or blocks a checkout; you decide what happens.

Flags, never blocks Shopify Flow

What WebDecoy does not do

WebDecoy does not score UCP checkout sessions, does not classify an agent’s intent inside checkout, and does not integrate with fraud platforms such as Sift, Signifyd, Forter or Riskified. It detects and flags; enforcement is something you turn on and approve.

Works With Your Existing Stack

Where WebDecoy installs, enforces, and sends its detections.

Shopify

Platform

WordPress

Platform

Cloudflare

Edge/WAF

AWS WAF

WAF

Fastly

Edge/CDN

Vercel

Platform

Netlify

Platform

Node.js SDK

Server

Splunk

SIEM

CrowdStrike LogScale

SIEM

Datadog

Logs

Webhooks

Custom

Where to Start

Whether you're on Shopify, building custom, or already behind a WAF.

Shopify

The WebDecoy Shopify app flags risky orders in your admin with the evidence behind them. It never cancels an order or blocks a checkout.

  • Orders linked to actors
  • Risk assessment on the order
  • Shopify Flow trigger for your own rules

Custom Implementation

Install the Node SDK or the JavaScript tag, add endpoint decoys to your API, and receive detections through the REST API and webhooks.

  • Local Web Bot Auth verification in the Node SDK
  • Endpoint decoys
  • Signed webhooks

At Your Edge

Push actor and IP blocks you approve into the WAF you already run. Monitor first, enforce when ready.

  • Cloudflare and AWS WAF
  • Fastly ACL
  • Auto-expiring IP blocks

UCP Opens the Door. We Watch Who Walks Through.

The shift to agentic commerce is happening. Start watching agent traffic on your store now.

Talk to Us Read the Deep-Dive