Is Henry Shopping Agent triggered by a user?

Yes. It is categorized as user initiated and acts within Henry's commerce workflow to carry out an authorized checkout.

Can robots.txt block Henry Shopping Agent?

Not reliably. It has no stable user-agent token, and Cloudflare's bot directory marks it as not following robots.txt. Enforce the decision at the edge after checking its signature.

How can I verify Henry Shopping Agent is genuine?

For a Henry checkout session, compare the agent's Web Bot Auth HTTP message signature with the public keys at https://www.henrylabs.ai/.well-known/http-message-signatures-directory. No stable user-agent pattern is published for identity checks.

Does this agent influence AI search or train a model?

Neither use is documented. Henry Shopping Agent is described as a checkout agent, so its direct site impact is whether a user-authorized purchase can be completed.

Henry Shopping Agent AI Crawler Guide

What is Henry Shopping Agent?

Henry Shopping Agent is a user-initiated purchasing agent from Henry Labs. Its recorded task is precise: it uses browser automation to execute checkout with the user's card and a signed mandate. It is an acting agent, not a crawler sent to build a public index.

Henry's wider commerce SDK supports merchant-catalog search, multi-merchant carts, checkout, and order tracking. The Shopping Agent belongs at the transaction end of that workflow. When it reaches a merchant site, it is trying to carry out a purchase that a user authorized through the Henry system.

Browser automation means the agent must work with the merchant's actual checkout experience. Whether it can reach the relevant pages and complete their required steps determines whether that purchase succeeds. This makes its traffic closer to an automated customer session than to routine SEO crawling.

A Henry Shopping Agent visit has no documented role in public AI answers, search indexing, or model training. Allowing it can enable a user-requested checkout. Blocking it can interrupt that checkout, but it is not described as a way to opt out of AI search or training data collection.

The agent has no stable published user-agent token. Cloudflare's bot directory lists it as an agent and points to Henry Labs' documentation, while identity keys are published at https://www.henrylabs.ai/.well-known/http-message-signatures-directory. Web Bot Auth signature validation is therefore the useful way to distinguish Henry's agent from an unrelated automated browser.

Cloudflare's bot directory marks Henry Shopping Agent as not following robots.txt and provides no user-agent patterns. A site cannot reliably isolate it with a robots.txt stanza. Merchants need to make the access decision where they can verify the signature and enforce route policy, such as the CDN or application edge.

Relevant for AI search

Is Henry Shopping Agent relevant for AI search?

Yes. Henry Shopping Agent collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

Henry Shopping Agent crawls and indexes pages so the AI search or assistant behind it can retrieve them at answer time. A page it has never fetched cannot be quoted, summarized, or linked in that product's answers, so most sites keep it allowed to stay citable. Blocking it removes your pages from that AI surface and hands those citations to competitors.

How to handle Henry Shopping Agent

Merchants that accept agent-executed checkout can allow Henry Shopping Agent, but the exception should be based on a valid signature rather than a guessed browser or user-agent pattern. Merchants that prohibit automated purchasing should deny the agent and expect Henry-based checkout attempts to stop.

There is no stable token for a useful robots.txt snippet, and Cloudflare's bot directory marks the agent as not following robots.txt. Do not create a broad rule that might catch ordinary browsers while trying to target Henry.

Verify the HTTP message signature with the Web Bot Auth keys at https://www.henrylabs.ai/.well-known/http-message-signatures-directory. Perform that check before granting any bot-specific edge exception.

Continue to apply the merchant's normal checkout authorization, inventory, and payment controls after identity verification. A genuine Henry signature identifies the agent; the signed mandate and the checkout itself still belong to the purchasing workflow.

Examples

A customer authorizes a purchase through a Henry-powered app, and Henry Shopping Agent opens the merchant checkout to execute it.
A merchant's CDN verifies the agent's HTTP message signature before allowing the automated browser into the checkout flow.
A retailer that does not accept agentic purchases blocks verified Henry traffic at the edge instead of relying on robots.txt.

Frequently asked questions about Henry Shopping Agent

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Henry Labs describes it as browser automation that executes checkout using a user's card and signed mandate.

Related bots

Amazon Kendra

Amazon Kendra is a managed information retrieval and intelligent search service that uses natural language processing and advanced deep learning model.

AI Assistant