Agentic Landmark · The Brief
Briefs on the infrastructure, authorization architecture, and commerce strategy of the agentic web: what brands need so agents can find, evaluate, and transact with them.
Designers now have a name for serving a human and an agent at once. But the emerging work is almost all about monitoring what an agent does. The harder problem comes first: the grant screen, where a consumer configures what an agent may do at all. AP2 shipped that infrastructure; the UX has not.
Google says you do not need llms.txt for Search, and it just added a Lighthouse check for it. Both are true, because they answer to different audiences. It is not a search signal; it is an agent signal, the site's way of telling a browser agent where to start. Google is now measuring both.
Forrester is right that agentic commerce calls for strategy over urgency, not panic. But "prepare now" implies the viable moment is ahead. For the brands on Google's Universal Cart launch list, it already arrived. The infrastructure timeline and the urgency timeline are the same timeline.
Every platform now offers retailers the agent intelligence it built for itself, on its own infrastructure. You keep the brand label; they keep the nervous system. The retailers who own the next decade will read that offer clearly and choose which layer to rent and which to own.
A frontier lab asked the Vatican for more scrutiny of AI, not less. The same question runs through commerce: the authorization architecture behind a delegated purchase decides whether an agent serves the person or the platform.
Adding AI features makes your platform smarter for the humans who use it; agent native means autonomous agents can call every capability directly, with delegated authority, and for commerce that architecture decision is being made today.
At I/O, Search stopped returning links and started building interfaces. That moves the job of optimization from citation-worthiness to structured-data-worthiness. You can write the best buying guide on the internet and still be absent from the comparison table the engine builds.
For thirty years the cart was something you filled, one store at a time. Google's Universal Cart inverts that: the agent assembles it across every merchant that can answer its questions. There is no browsing phase to abandon. The cart is built from a brief.
Most coverage reads the Stainless acquisition as a developer-tools story. It is a connectivity story. Anthropic is vertically integrating the layer that turns an API spec into the MCP servers Claude agents use to reach your catalog, inventory, loyalty, and checkout.
Google's I/O announcements are not previews, they are production. The Universal Cart, the AP2 authorization layer, and UCP expansion are shipping to a billion AI Mode users. The launch merchant list is the first public ranking of which brands are inside the infrastructure.
