AgentStack serves tenant storefront vitrines from the hosting plane — static bundles with commerce boot metadata.
Public promo vitrine (sandbox catalog):
https://agentstack.tech/s/2/demo-store/
Inspect layout, cart drawer, and checkout bridge without provisioning your own bucket first.
MCP health: hosting.demo_store.status — catalog row count, published build id, manifest bucket.
After publish:
https://agentstack.tech/s/{project_id}/{bucket_name}/
SPA client-router storefronts may use /a/{project_id}/{bucket_name}/ when configured.
Create and publish via Storage → Sites or MCP hosting.site.quick_start + commerce.storefront.hosted_publish.
Embed commerce client code without bundling the full SDK:
https://agentstack.tech/sdk/v{version}/commerce.esm.js
Example (version from your deployment):
<script type="importmap">
{
"imports": {
"@agentstack/commerce": "/sdk/v0.4.14/commerce.esm.js"
}
}
</script>Build pipeline publishes commerce.esm.js with Brotli/gzip at the edge. Keep version pinned in production.
{
"action": "commerce.storefront.hosted_manifest",
"params": { "project_id": 42 }
}{
"action": "commerce.storefront.hosted_publish",
"params": { "project_id": 42 }
}Guest cart on /s/... deeplinks to platform checkout when the user signs in — see commerce/WALLET_AND_PAYMENTS.md.
- Edge readiness: if
/s/...404s immediately after publish, callhosting.site.edge_healthor republish from Sites UI. - SEO: tenant meta via Storage → Sites → SEO and
GET /api/seo/meta. - CRM link: deal
linked_order_idis read-only until commerce–CRM bridge automation lands.