Product Feed vs Agent-Readable Catalog: What Merchants Should Publish Now
A product feed helps listing and search surfaces understand merchandise; an agent readable catalog helps software buyers act on merchandise. Merchants should keep the shopping feed for discovery, then publish a catalog that exposes action URLs, policy terms, checkout routes, provenance, and current commerce state for agent evaluation.
Google Shopping feeds and Merchant Center data remain useful for ads, product listings, and search-style ranking. Agent-readable catalogs add the operational layer: what an agent may do, which checkout route is official, which policy applies, who operates the merchant surface, and how order evidence returns to the buyer.
Product Feed vs Agent-Readable Catalog
| Merchant question | Product feed answer | Agent-readable catalog answer |
|---|---|---|
| Where should the item appear? | Search listings, ads, shopping tabs, marketplaces, and comparison surfaces. | Agent workflows, shopping assistants, checkout agents, support agents, and partner APIs. |
| What facts are published? | Title, image, price, category, availability, shipping hints, and product URL. | Stable product IDs, variants, compatibility, policy URLs, checkout routes, allowed agent actions, and support paths. |
| Can a software buyer act? | Usually by sending a human shopper to a product detail page or hosted checkout. | By building a cart, requesting a quote, starting a machine checkout, or routing a support request under merchant rules. |
| How are policies read? | Policies may sit on separate pages or appear as lightweight merchant attributes. | Return terms, refund policy, shipping rules, warranty limits, support contacts, and escalation paths are linked from the catalog. |
| How is trust checked? | The surface relies on merchant account metadata, listing status, and platform review. | The catalog points to a public .agent identity, operator proof, source record, version, and receipt route. |
What Product Feeds Still Do Well
Product feeds are still the cleanest way to send merchandised product facts into listing systems. They help channels compare titles, images, prices, availability, merchant categories, and landing pages at scale. A retailer should keep feed quality high because agents often begin with the same discovery surfaces humans use.
Google's Universal Commerce Protocol launch connects Merchant Center data with conversational commerce and describes new attributes that go beyond keywords, including answers to common product questions, compatible accessories, and substitutes. That is a clue for merchants: a feed built only for listing placement is no longer the full commerce artifact.
What an Agent-Readable Catalog Adds
The UCP homepage describes a common language for platforms, agents, and businesses, with capabilities such as catalog search, cart building, identity linking, checkout, and order management. The catalog therefore has to carry more than display facts. It should tell an agent how to evaluate an offer, act within merchant rules, and preserve evidence after checkout.
The Agentic Commerce Protocol focuses on programmatic commerce flows between buyers, AI agents, and businesses, including agent-ready checkout and REST or MCP-compatible integration patterns. That makes checkout configuration part of the catalog story, not a separate afterthought.
BMOS shows the merchant-facing version of this pattern: a standardized catalog feed with schema.org plus ACP and UCP extensions, current pricing, variants, images, availability, machine checkout links, refund policy, terms, and agent metadata. For merchants, that kind of feed turns product data into an action surface.
Fields Merchants Should Publish Now
- Canonical product ID, SKU or GTIN, normalized title, brand, description, category, media, and product URL.
- Variant structure: size, color, bundle, subscription, replacement part, compatibility, and substitution guidance.
- Current price, currency, availability, fulfillment windows, shipping options, tax handling, and stock constraints.
- Human checkout URL, machine checkout URL, cart-building route, quote route, session expiry, and receipt route.
- Return policy, refund policy, warranty terms, shipping policy, privacy terms, support contact, and escalation path.
- Allowed agent actions, blocked actions, purchase limits, buyer confirmation rules, and handoff conditions.
- Catalog version, update timestamp, source system, publisher identity, proof links, and change log.
- Public .agent identity with agent.json, SKILL.md, llms.txt, endpoint list, policy links, and operator proof.
Example Agent-Readable Catalog Record
{"merchant":"northstar-outfitters","identity":{"headless_domain":"northstar.agent","agent_json":"https://northstar.agent/.well-known/agent.json","skill_md":"https://northstar.agent/SKILL.md","llms_txt":"https://northstar.agent/llms.txt"},"catalog":{"feed_url":"https://catalog.northstar.example/agentic-commerce.json","schema":"schema.org Product plus ACP and UCP extensions","updated_at":"2026-05-21T09:00:00Z"},"product":{"id":"sku-7421","name":"Trail Jacket","variants":["small","medium","large"],"availability":"in_stock","price":{"amount":"84.00","currency":"USD"}},"checkout":{"human":"https://northstar.example/checkout","machine":"https://machine.checkout.example/northstar","protocols":["ACP","UCP","x402-ready"]},"policies":{"returns":"https://northstar.example/returns","terms":"https://northstar.example/terms","support":"mailto:support@northstar.example"},"agent_actions":{"allowed":["compare","quote","cart","checkout_request","order_status"],"blocked":["auto_substitute_without_confirmation"]}}Where HeadlessDomains.com Fits
HeadlessDomains.com gives the commerce surface a public identity anchor. A merchant can attach the BMOS feed, ACP or UCP checkout routes, policy pages, proof links, endpoint list, and support routes to a .agent identity that agents can inspect through command-line and API workflows.
This identity layer complements How to Make Your Store Discoverable to AI Shopping Agents, the Agentic Commerce hub. Catalog data tells agents what can be bought. The identity record tells agents which commerce surface is official, who operates it, which manifests are authoritative, and where payment or support evidence should return.
A Practical Publishing Order
- Clean the existing product feed so titles, prices, images, availability, variants, and product URLs are consistent.
- Create the agent-readable catalog with policy, checkout, provenance, and action fields.
- Expose the feed as JSON at a stable URL and document the update cadence.
- Connect ACP or UCP checkout routes where the store is ready for agentic purchase flows.
- Publish agent.json, SKILL.md, and llms.txt for the merchant surface.
- Attach the catalog, policies, endpoints, and proof links to a public .agent identity.
- Test shopping prompts against discovery, cart, checkout, return, and order-status flows before inviting partners.
Related Reading
- How to Make Your Store Discoverable to AI Shopping Agents
- ACP vs UCP vs BMOS
- AI Shopping Readiness Checklist
- Agent Payments Require Identity, Authorization, and Receipts
- The Agent Identity Stack
FAQ
Is a product feed still worth publishing?
Yes. Product feeds remain useful for listing surfaces, ads, search systems, marketplaces, and first-pass discovery. The agent-readable catalog extends that foundation into action, checkout, policy, and identity.
What is an agent-readable catalog?
An agent-readable catalog is a machine-readable product and commerce record that lets software buyers inspect products, policies, checkout options, provenance, and allowed actions without scraping a visual storefront.
How is this different from schema.org Product markup?
Product markup helps search and structured-data consumers understand a page. An agent-readable catalog can include the same product facts plus cart routes, checkout links, refund terms, support paths, identity records, and protocol metadata.
Where do ACP and UCP fit?
ACP focuses on agent-ready checkout flows between buyers, agents, and businesses. UCP defines a broader commerce language across discovery, cart, checkout, identity linking, order management, and post-purchase support.
How does a .agent identity help merchants?
A .agent identity gives agents one public place to inspect the merchant operator, catalog URL, policy URLs, checkout endpoints, manifests, proof links, and support routes before they recommend or buy.
Do Headless Domains require browser-native DNS resolution?
No. Headless Domains are headless names for agents and workflows. Agents can use Headless Domains and SkyInclude infrastructure through command-line and API workflows; browser resolution is only a conventional browser user-experience topic.
What should merchants publish first?
Start with one publishable unit: expose the catalog as machine-readable JSON, link the official ACP or UCP checkout routes, and attach the commerce surface to a public .agent identity on HeadlessDomains.com. Then agents can inspect product facts, policy, checkout, and provenance before a recommendation or purchase.