Agent Stamp

ChatGPT can find your products. Can it check out? ChatGPT, Claude, Perplexity, Grok and Google's agents now shop for people. Many get stuck at a captcha, a required account or a firewall, and WooCommerce never tells you. Agent Stamp does. What you get, free

• The agent funnel. How many AI agents visited, opened a product, built a cart, reached checkout and paid, for the last 7, 30 or 90 days.
• Why they did not buy, in money. Captcha, account required, 403 from a security plugin, out of stock, no shipping, a rejected field, a failed payment. Each reason shows the cart value your store stopped and what to change.
• A 0-100 readiness score with one-click fixes for guest checkout and letting signed agents skip the captcha.
• A stamp on every order: Human, ChatGPT, Claude, Likely agent, Unattended, API or Unknown, plus a Buyer column on the orders list.
• Evidence for disputes. Download the JSON evidence record for any order.
• A weekly email with agent revenue and the top reasons agents failed. Quiet weeks stay quiet.

How it works

1. Install and activate. WooCommerce must be active.
2. Open WooCommerce > Agent Stamp > Readiness and apply the one-click fixes.
3. Watch the Agents tab fill in as agents visit. Every new order gets its stamp.

Nothing is blocked unless you turn a rule on. Signatures are checked on your own server, and checkout traffic is not sent to another company. A person's visit is not recorded. Agent readiness The Readiness tab scores the store from 0 to 100: whether the store is live or still in coming soon mode, guest checkout, captcha at checkout, robots.txt for shopping crawlers and agents, product data and barcodes, product markup, shipping and returns pages, the Store API, signature support, and agents refused in the last 30 days. Guest checkout, and letting signed agents skip the captcha, are one click. The same outside checks run free at https://getagentstamp.com/check. Rules Nothing is blocked or held unless you turn a rule on. An agent with a verified signature is never refused or held by a rule.

• Signed agent: always accepted. Optionally skips hCaptcha or Simple Cloudflare Turnstile. People still see the captcha.
• Likely agent: allow, or hold for review. Never refused, since a person may have placed it.
• Unattended: allow, hold the paid order, or refuse and ask the agent to identify itself. No person used the place-order control, and no agent named itself.
• Every other checkout has no rule: a declared name, an agent named by the payment, this store's REST API, an agent protocol, a person, and Unknown.
• Agent Stamp Pro, a separate plugin, adds its own rules: a card-testing guard, a buyer confirmation email for agent orders, holding agent orders until the buyer confirms, and a dispute reply built from the order.

The stamp on each order Agent Stamp writes one line on the WooCommerce order you already open.

• Human, when the checkout came from an ordinary browser and carried no agent signature.
• A named agent, when the request has a valid Web Bot Auth signature, or when the user-agent is a published agent such as ChatGPT-User, Claude-User, Perplexity-User, Google-Agent, or GrokAgent.
• Likely agent, when a trusted click placed the order but the page saw at least two signs that a program drove the browser. It is labeled likely, not proof.
• A named agent from the payment, such as ChatGPT (payment), when the order came from Stripe's or PayPal's own agent checkout, or Stripe named the agent on the payment. Many agents look like an ordinary browser, so the payment is a second place to catch them.
• Unattended, when the checkout page saw no person use the place-order control, or the browser reported itself as automated.
• API, when the order was created through the REST API or a commerce protocol channel, not the checkout page.
• Unknown, when the request is anything else, including a signature that does not check out, or a crawler such as GPTBot claiming to check out.

The orders list gets a Buyer column. The Orders tab shows the last 30, 90 or 365 days: how many orders were not a person, the revenue from them, and the orders, revenue and share for each buyer. Each order box has a JSON download of the evidence record and its fingerprint, for a dispute or a chargeback reply. A claimed name is not treated as proof. If a request says it is ChatGPT and the signature fails, the order stays Unknown. The signature is checked on your server. Checkout traffic is not sent to another company. Once a week, if AI agents visited or any order was not a person, the site admin gets one email: how many orders were not a person and the revenue from them, how far agents got, the top reasons they failed, and the orders. Weeks with neither stay quiet. What it cannot see Requests a CDN or firewall refused before WordPress ran, pages a full-page cache served, and agent browsers that look like a person until checkout. The cart value counts only carts the store itself stopped with an error.

1.5.7

• The agent key directory is fetched with wp_safe_remote_get(), so WordPress checks the URL again at request time, and the connection is pinned to the addresses that passed the plugin's own public-address check, so a DNS answer that changes in between cannot redirect it.

1.5.6

• Orders tab: orders, revenue and share for each buyer.
• Order box: download the evidence record as JSON.
• The weekly email says how many orders were not a person and the revenue from them.

1.5.5

• Agent visits are kept for 90 days. The Agents tab shows the last 7, 30 or 90 days, and the Orders tab the last 30, 90 or 365 days. Nothing in the free plugin waits for Pro.

1.5.4

• Settings page styles load as a stylesheet.

1.5.3

• Agents tab: an agent stopped by Simple Cloudflare Turnstile on the block checkout, or by an hCaptcha token error, is listed as stopped by a captcha instead of a server error.

1.5.2

• External services now lists Freemius, which runs the Pro upgrade and trial, and the Stripe payment check for stores that use the WooCommerce Stripe Gateway.

1.5.1

• Readiness flags a store still in WooCommerce coming soon mode, where agents and shoppers see a placeholder.
• Agents tab: the first agent shows as soon as it visits, a failed add to cart is no longer counted as reaching checkout, a thank-you page for an unpaid order is no longer counted as paid, and the plugin that refused an agent is named.
• Checkout: a shopper who only clicks a wallet button in a payment frame is no longer stamped Unattended.
• Rules: one Save keeps both the rules and the weekly email setting.
• The Agents tab names the page cache, which can hide agent visits.
• Scan past orders opens the Orders tab, and long tables fit a phone screen.

1.5.0

• Agents tab: every AI agent visit from the first page to the order, why agents did not buy, the cart value the store stopped, and the fix for each reason.
• Readiness tab: a 0–100 score for agents with one-click fixes for guest checkout and letting signed agents skip the captcha.
• Rules, all off by default: signed agents can skip hCaptcha and Turnstile, Likely agent can be allowed or held, and Unattended can be allowed, held, or refused. Pro adds the card-testing guard, buyer confirmation, holds until the buyer confirms, and dispute replies.
• The weekly email also goes out when agents visited, and leads with where they failed.

1.4.0

• Trends, CSV export, alerts and the Buyer filter moved to the separate Agent Stamp Pro plugin.

1.3.0

• Likely agent stamp for agent browsers that click like a person.
• Evidence record on each order, a private note when the buyer was not a person, and a JSON download for a dispute reply.
• Buyer filter on the orders list.
• Orders, revenue and share by stamp for the last 30 days.
• Orders created through the REST API or a commerce protocol are stamped API, or with the agent's name.
• A checkout that names an AI crawler is Unknown.
• The weekly email leads with revenue from orders that were not a person.

1.0.0

• First release. Order stamp, order list column, weekly email.