What is Lane Agent?
Lane Agent visits a merchant because a person has asked Lane to discover something to buy and complete a purchase. Lane describes it as part of its agentic commerce infrastructure. The request has a shopper and a transaction goal behind it.
This makes Lane Agent different from an indexing crawler. It may need to read merchandise information and move through the merchant's purchase flow, but Lane says it does not crawl autonomously. Its operator page ties activity to an explicit end-user purchase request.
Lane also says the agent identifies itself, observes merchant access policies, and does not bypass controls or evade detection. A merchant can still require the same authentication, availability checks, payment protections, and confirmation steps that apply to other clients. Agent identity is not permission to skip those controls.
Lane Agent has no documented role in building an AI search index. The source record also gives it no model training purpose. Blocking it can interrupt a shopper's delegated purchase, but this identity is not a documented control for AI search inclusion or training collection.
The strong identity signal is a Web Bot Auth signature, not a user-agent token. Lane uses HTTP Message Signatures and publishes its keys at https://agent.getonlane.com/.well-known/http-message-signatures-directory. A valid signature establishes that Lane sent the request; the merchant must still decide whether the requested action is allowed.
No stable user-agent token is recorded for Lane Agent, so a dedicated robots.txt group would not target it reliably. Robots behavior is unknown in this catalog, and Cloudflare's bot directory lists followsRobotsTxt as false. Merchants that need an allow or deny rule should make that decision at the CDN, WAF, or application layer after checking the signature.
