Topics: AI storefront, product discovery, merchant subdomain, HTML, JSON, MCP, A2A, canonical URLs
Questions answered
- What is an AI storefront?
- Does it replace the merchant website?
- How should an agent discover a merchant's endpoints?
- Is this company site a merchant catalog?
A parallel product-information surface
Evidence basis: implementation_review · Section citation
Catalog's merchant AI storefront presents selected product information in forms that agents can retrieve and interpret. It can operate on a brand subdomain alongside the existing consumer website. The consumer website remains the destination for the merchant's checkout, customer account, orders, and purchase-time terms unless a separately confirmed integration changes that arrangement.
The product storefront implementation resolves the merchant for the requested hostname and serves information in that merchant's context. Correct configuration and published content are prerequisites. An arbitrary ai.brand-domain hostname does not become a Catalog storefront by naming convention alone, and a configured DNS record does not prove that product content is being served successfully.
Sources: Catalog website · Machine-readable product enrichment
Product and collection retrieval
Evidence basis: implementation_review · Section citation
The reviewed merchant implementation includes readable product pages, structured JSON product documents, catalog listing/search, collection discovery, brand facts, and an agent guide. Product URLs can follow Shopify handles or mirror the merchant's original paths, depending on the store. Agents should follow the actual URLs returned in discovery or listing responses rather than manufacture paths from product titles.
Collection paths and availability can differ by store. A paginated product API is the documented bulk retrieval path in the reviewed implementation; the presence of feed-related code does not prove that a downloadable bulk feed is enabled or published. Read the target merchant's live guide and API specification to establish the available contract.
Sources: Catalog website
Product insights and decision context
Evidence basis: implementation_review · Section citation
The storefront implementation can include structured product insights with provenance and decision-guide content such as use cases, constraints, variant choices, comparisons, and evidence references. Availability depends on the product record and configuration. A section type supported by the renderer does not imply that every product has content of that type.
This material helps an agent connect product facts to a buyer's question. Use the cited evidence and preserve distinctions between manufacturer facts, review observations, and editorial conclusions. For comparisons, confirm that the alternatives and variants being compared actually match the user's market, budget, and constraints.
Sources: Machine-readable product enrichment · Ecommerce Product Data Infrastructure Guide
Protocol availability belongs to each live hostname
Evidence basis: implementation_review · Section citation
The separate merchant storefront implementation contains MCP, A2A, OpenAPI, agent discovery and skill-related code. Those code paths were inspected as implementation evidence; this reference does not certify their live operation for every merchant. Use the exact target hostname's published descriptors and test the advertised operation before relying on it.
The Catalog company reference at ai.getcatalog.ai is deliberately a public, read-only HTTP document collection. Its OpenAPI describes actual JSON reads on this hostname. It has no merchant products, tool execution, MCP server, A2A task service, registration, checkout, or downloadable skill. Do not transfer a merchant storefront's advertised capabilities onto this hostname.
Sources: Catalog website
What counts as published and what counts as used
Evidence basis: editorial_guidance · Section citation
Publication means that the intended product representation can be fetched successfully from its destination. Agent access means an external client requested it. A sampled assistant answer mentioning or displaying the product is a further observation. A shopper click, an attributed order, and incremental revenue are additional, distinct outcomes.
A useful launch check verifies hostname ownership, DNS, TLS, canonical URLs, content types, page/JSON consistency, product selection, policy links, redirects, and unknown-route behavior. After launch, use evidence from the relevant measurement surface to assess access or visibility. The existence of a machine-readable page cannot establish that an assistant has indexed it or will recommend it.
Sources: Catalog website · Product data quality · Dark traffic in agentic commerce