Headless Storefront on the GRAJ protocol. One fee. 195 countries. Join the protocol.
A brand with a designed storefront should not have to abandon it to sell wholesale, and a protocol that insists on owning the front end is a platform. Headless means the catalog, orders and settlement are reachable from whatever interface the brand already has.
Design, copy and the shopping experience are what a brand competes on. Anything that requires giving those up in exchange for infrastructure is asking for the wrong trade.
Prices, tax and totals are resolved by the protocol regardless of what the front end sends. That is the same rule as the hosted checkout: a total a browser computes is a total a browser can change.
The versioned HTTP API can be read for catalog and written to for orders, which is most of what a custom storefront needs. What is missing is the packaging around it — components, a documented storefront flow and webhooks for order events.
The API exists; the headless storefront kit does not. A developer can build against the HTTP surface today, and this page does not offer a drop-in they would go looking for.