Glossary

The words Lens uses, one line each.

Everyday words

AI agent: Software that acts for a person: it visits sites, reads what they publish and, where a site allows it, buys.
Agentic commerce: Selling to AI agents as well as to people, with products, prices, terms and payment they can read and act on.

Report words

The model

Stage: One of four steps an AI agent has to clear at your site before it can buy and prove the deal.
Check: One thing Lens looks for, such as whether your prices say whether tax is included.
Fix: A check that did not pass, with who usually fixes it and how long that typically takes.

The four stages

Discoverable: Agents get in and read your products and prices as data.
Agreeable: Agents know who sells what, for how much, and on what terms.
Transactable: Agents can check out and pay through an interface built for them.
Provable: The payment carries a record of the agreement that anyone can check.

A stage's state

Reached: Every check the stage needs passes, and every stage under it is reached.
Next: The nearest stage not yet reached: the one to work on now.
Not yet: A stage further up, after the next one.
Can't tell: Lens couldn't check enough of the site to say.

A check's state

Passed: Lens found what this check asks for.
To fix: Lens did not find it. This is something to fix.
Waiting: This needs an earlier check on the same ladder to pass first.
Not checked: Lens could not check this from outside the site.
Doesn't apply: This check does not apply to this site.

Groups of checks

Catalog: Can an agent find and read what is sold?
Purchase: Can an agent buy without a browser?
Access: Does the site answer an agent that says honestly what it is?
Terms: Can an agent know the terms it would agree to?
Binding: Does the payment carry the agreement?
Seller: Who is selling?
Product: Exactly what is sold?
Price: Is the price the agent sees the price that will be charged?
Agreement record: Is the agreement offered as one record, fixed by its hash, before the buyer commits?

Standards

UCP, the Universal Commerce Protocol: A published way for a shop to tell an AI agent what it sells and how to buy it, announced by Google with Shopify and others.
ACP, the Agentic Commerce Protocol: OpenAI's and Stripe's protocol for agent shopping. A seller may publish a discovery document saying it takes part.
AP2, the Agent Payments Protocol: Google's protocol, now at the FIDO Alliance, for a person to authorize an agent to buy a specific thing at a specific price.
x402: A way for a server to answer a request with a price, using the long-unused HTTP status 402, so an agent can pay and retry.
MPP, the Machine Payments Protocol: Stripe's and Tempo's way for an agent to pay per request, carried in HTTP's standard authentication headers.
MCP, the Model Context Protocol: The standard way an AI model calls tools. UCP rides on it, so a shop's catalog is reachable as a tool call.
LCP, the Legal Context Protocol: Integra's protocol for publishing, in a machine-readable way, the terms a purchase is made under.
ATR, the agreement transaction record: The record of what was agreed in one transaction: the offer, the terms and the parties, assembled as a document.
Web Bot Auth (RFC 9421 signatures): An agent signs its requests with a key it publishes, so a site can tell which agent is calling.
robots.txt (RFC 9309): The file at the root of a site saying which automated clients may fetch what.
schema.org Product: Structured data embedded in a page describing the product and its price, readable without running the page's scripts.
GTIN and GS1 Digital Link: The global barcode number for a product, and the web address form that resolves it to the product's own record.
LEI (ISO 17442): A twenty-character code identifying a legal entity, issued under a global register anyone can query.
VIES (EU VAT validation): The European Commission's service for checking that a VAT number is valid and who it belongs to.
BIMI and Verified Mark Certificates: A certificate saying a trademark belongs to the domain that publishes it, issued after a verification process.
did:web and DID Configuration: A way to publish signing keys at a domain and to link that domain to an identifier in both directions.
SCITT and transparency logs: An append-only log of signed statements. Anyone gets a receipt proving their entry is in it, checkable without asking the log again.
Digital Product Passport: A signed record of what a product is — its name, description, image and measurements — issued by the seller or the brand.
PriceSpecification: The structured form of a price, which can say whether tax is included and for which jurisdiction.
priceValidUntil: A date after which the published price should not be relied on.
ItemAvailability: Whether an item is in stock, published as a value rather than as words on a page.
OfferShippingDetails: What delivery costs, where it goes, and how long it takes, published per offer.
MerchantReturnPolicy: The returns policy as structured data: the window, the conditions, who pays return shipping.

Technical words

These appear only on a report's Technical page and in its record.

Outcomes

Metmet: The evidence captured satisfies the criterion.
Not metnot_met: The evidence captured does not satisfy the criterion. The remedy says what would.
Not testednot_tested: Lens deliberately did not run this check, and says why. It is never counted as a failure.
Inconclusiveinconclusive: Lens could not get a clear answer, for a reason the result names, such as a timeout or a challenge seen from one vantage only.
Does not applyn/a: The criterion has nothing to look at on this site, such as product identifiers where the site shows no products, so it counts neither as met nor as not met.

The engine's words

Level: How far up a dimension's ladder the subject reached. Every site starts at level 1, which asks nothing.
Ceiling: The level a dimension would reach if every criterion Lens could not test had been met.
Terms digest: The hash of the terms, published by the seller before anyone buys, so an agent can tell the terms it is shown are the ones published.
Evidence: The exact bytes Lens received, kept and named by their SHA-256, which every finding cites and anyone can re-hash.
Identity: Who Lens said it was when it made a request: anonymous, a UCP platform, or signed, recorded with every finding.
Vantage: Where a request came from: Lens's Cloudflare Worker, or a relay outside Cloudflare asked only after the Worker was refused.