Stores
Brand identity and agent scoping — each store has its own name, listings, and API key
A store is the brand layer in ListBee. It holds the display name, bio, and avatar that appear on product pages. Each store has exactly one API key — when an agent authenticates, it operates within that store’s scope.
Stores sit between accounts and listings:
One account can have multiple stores. All stores on an account share the same Stripe connection — the human does KYC once, every store can sell.
How it works
Stores are created through the bootstrap flow. When an agent bootstraps, it provides a store name. The API creates the store, generates an API key, and returns both. The agent uses that key for all subsequent requests.
Everything the agent does is scoped to its store. GET /v1/listings returns only that store’s listings. GET /v1/orders returns only orders from that store’s listings. Agents never see resources from other stores on the same account.
Key fields
Store readiness
Store readiness tells the agent whether listings in this store can accept payment.
The only store-level gate is Stripe. Once connected, sellable becomes true and listings can take payment immediately after publish.
Store landing page
Every store has a public landing page at buy.listbee.so/{slug}. It shows all published listings with the store’s branding. Useful for sharing a single link or providing a URL during Stripe Connect verification.
Example
Multiple stores
A second agent bootstrapping with the same email creates a new store on the existing account. The second store inherits the Stripe connection — it’s immediately sellable if Stripe was already connected.
Each store has its own API key, listings, webhooks, and slug. Stores are independent brands under one billing account.
Related
- Authentication — how to create a store via bootstrap
- Readiness — how readiness works at store and listing levels
- Listings — creating and managing listings within a store