Stories
Why now: search agents, browser agents, commerce protocols, and site Assistants
22 July 2026 by Open for Agents
Search agents, browser agents and site-provided Assistants are emerging at the same time. Open for Agents gives website owners one reviewed place to decide what those agents may know and do.
That does not mean every agent works in the same way. Search systems, browser agents, commerce systems and on-site Assistants have different jobs and different routes into a website. The useful common ground is the website owner's approved facts and capabilities.
One product family, different jobs
WordPress is the Open for Agents flagship: Core lets an owner discover, review, publish and validate the capabilities agents may know and use.
The public Open for Agents Shopify app has a different job. It independently verifies how intended catalogue state appears across supported AI shopping surfaces and public-store evidence. It does not present itself as Shopify's agent control layer and it does not change the store.
Any-Web explores a third job: a grounded, cited, read-only conversation over reviewed public material. It remains a controlled preview rather than a generally available product.
Search still starts with the public web
Search systems crawl, index and revisit public pages. Google's guidance for generative Search features says the familiar foundations still matter: pages need to be crawlable and indexable, important information should be visible and useful, and structured data should agree with the page.
Google also says it ignores llms.txt for Search inclusion and ranking. Open for Agents can publish llms.txt as an optional compatibility resource for other clients that choose to read it, but the file is not a substitute for sound Search foundations.
Browser agents can use pages or reviewed tools
A browser agent can work from the visible interface and accessible page structure. When the browser supports WebMCP, a website can also offer explicit tools with typed inputs and structured results. This reduces guesswork, but it does not remove the need for authorization, review, or user approval.
WebMCP remains an emerging proposal, and compatible browser support is not universal. Open for Agents Core keeps the owner's reviewed catalog separate from any one delivery format so a protocol change does not become the site's source of truth.
Commerce protocols are another projection
Commerce agents may use systems such as the Universal Commerce Protocol to understand approved catalog and transaction capabilities. UCP is an emerging protocol, not an Open for Agents certification and not proof that a particular merchant or website supports it.
A commerce projection should be generated from current, owner-approved product data. It should not become a second catalog that quietly drifts away from the live store.
A site-provided Assistant reaches visitors directly
Not every visitor arrives with a compatible agent. The optional Open for Agents Assistant provides an on-site conversation interface for the same reviewed capabilities. Visitors can ask naturally, see the relevant tool activity, approve consequential actions, and use Undo where the underlying action is supported and reversible.
Core decides what agents may know and do. The separate Assistant add-on provides the conversation interface. The secure hosted service operates the model connection and the site's reviewed capability boundary. That hosted service is not required for ordinary direct WebMCP access by a compatible browser agent.
Checkout, payment, order placement, authentication and sensitive account actions remain human-controlled.
Four ways a visitor or agent may meet the site
| Surface | What it receives | Owner boundary |
|---|---|---|
| Without a structured agent surface | Facts and controls inferred from the page | The public page and ordinary site permissions |
| With Open for Agents Core | Reviewed typed tools and structured results | The owner's canonical reviewed catalog |
| With a commerce projection | Current approved catalog data in a compatible commerce format | The live store remains authoritative |
| With the optional Assistant | Natural conversation, visible tool use, approval, and supported Undo | The same reviewed catalog plus the Assistant's secure operating controls |
No single emerging protocol should be treated as the canonical source of truth. The durable part is the owner's reviewed control layer; Search pages, WebMCP tools, commerce projections and the optional Assistant are different ways to publish or use approved information.
The Open for Agents demo store is synthetic product demonstration content. It is not a genuine merchant and must not be represented or submitted as one.
See the reviewed control layer
- Start with Open for Agents Core, then install the current release from the official WordPress.org listing.
- Understand the optional Open for Agents Assistant, including its separate add-on and hosted-service boundaries.
- Try the live Storefront Assistant to see reviewed tools, visitor approval and supported Undo in context.