Stories
Why now: search agents, browser agents, commerce protocols, and site Assistants
by Open for Agents · Updated
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.
WordPress, Shopify, and Any-Web solve different problems
Open for Agents began with WordPress. Core lets an owner discover, review, publish and check the capabilities agents may know and use.
The public Open for Agents Shopify app has a different job. It checks whether product information shown by supported AI shopping services still matches the merchant's live store. It does not control Shopify agents or change store data.
Any-Web explores a third job: a read-only conversation over selected public Open for Agents material, with links to the sources used in each answer. It is a demonstration, not a service offered to other websites.
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 choices in its own catalogue and can publish them in each supported format, so a protocol change does not require the owner to make those decisions again.
Commerce formats should follow the live store
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.
Commerce data for agents should come 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 connects to the model and lets it call only the capabilities the owner published. 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
| How it reaches the site | What it receives | What the owner controls |
|---|---|---|
| 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 capabilities the owner approved in Core |
| With a commerce format | Current approved catalog data in a compatible format | The live store remains authoritative |
| With the optional Assistant | Natural conversation, visible tool use, approval, and supported Undo | The same approved capabilities plus the Assistant's security and approval rules |
No emerging protocol should replace the owner's decisions. Search pages, WebMCP tools, commerce formats and the optional Assistant can all use the information and capabilities the owner approved.
The products in the Open for Agents demo store are fictional and exist only to demonstrate the experience.
Try the WordPress plugin and Storefront demo
- 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.