Headless commerce
Headless commerce separates the storefront a shopper sees from the commerce platform that holds the catalogue and processes orders, with the two communicating over an API.
It is neutral for agent readiness by itself. What decides the outcome is whether the storefront renders its facts on the server or assembles them in the browser.
A headless storefront that server renders its product pages is as readable as any other. One that ships an empty shell and a bundle publishes no price, no availability and no variants to anything that read the response and stopped.
Why it matters to a store
Teams often assume a good API covers this. It does not: an API serves consumers who know it exists, have credentials and read documentation, and an agent arriving from a shopper’s question has none of those.