Store summary for AI assistants (llms.txt)
A Markdown summary of the store in the llms.txt format: its name, description, website and product count, the categories and subcategories it sells with product counts, and its featured products and collections, each linking to the storefront. It carries only what the storefront already shows and is regenerated as the catalog changes.
{store} is the store id or store code. The file is published by default; a wholesale store
publishes it only once the merchant turns it on, and the merchant can turn it off at any time.
A store on a trial or with a lapsed subscription returns 404. No API key required.
AI assistants look for /llms.txt at the root of a site, so a storefront typically forwards its
own /llms.txt to this address.
Authorizations
API Key Authentication
Use your API key in the Authorization header:
Key Types:
Secret Keys (Server-Side Only):
- Format:
tybrite_sk_live_*(production) ortybrite_sk_test_*(sandbox) - Full read/write access to all endpoints
- ⚠️ NEVER expose in client-side code or public repositories
- Required for: write operations, authentication, payment verification, AI recommendations
Publishable Keys (Client-Safe):
- Format:
tybrite_pk_live_*(production) ortybrite_pk_test_*(sandbox) - Read-only access (GET requests only, plus POST semantic search)
- ✅ Safe for client-side JavaScript, mobile apps, and public code
- Allowed for: browsing products, search, CMS content, pricing queries
Endpoint-Specific Requirements:
- Authentication endpoints (
/v1/auth/*): Secret key required - Payment verification (
POST /v1/payments/verify): Secret key required - AI Recommendations (
POST /v1/recommendations): Secret key required - Semantic Search (
POST /v1/search): Both key types allowed (read-only operation) - All write operations: Secret key required
- All read operations: Both key types allowed
Using a publishable key for restricted operations returns 403 Forbidden.
Path Parameters
Response
The store summary as Markdown.
The response is of type string.

