Sandbox Quickstart
CommerceBackend’s public proof surface is a hosted sandbox for agent-native commerce flows. Use it to inspect seeded listings, create offers, evaluate purchase-policy behavior, and run checkout in Stripe test mode without touching production money.
What works now
- Agent-facing discovery files
- Seeded listing search and listing inspection
- Offer creation and accepted-offer checkout flow
- Purchase-policy evaluation before checkout
- Stripe test-mode checkout sessions
What this is not
- Not a production marketplace
- Not real-card processing
- Not seller payouts or Stripe Connect
- Not refunds, disputes, taxes, or multi-seller carts
- Not merchant connector sync
Base URLs
Landing: https://www.commercebackend.com
Sandbox API: https://api.commercebackend.com
Health: https://api.commercebackend.com/health
The sandbox API is live at the hostname above in Stripe test mode. Requests are rate limited per IP.
Minimal request shape
Authorization: Bearer <demo buyer api key>
Content-Type: application/json
X-Request-Id: sandbox-demo-001
Fastest builder flow
1. Read llms.txt / llms-full.txt
2. Fetch or search seeded listings
3. Create an offer or checkout intent
4. Observe whether policy auto-approves or requires operator approval
5. Complete Stripe test checkout
6. Inspect the resulting order state
Example calls
curl https://api.commercebackend.com/health
curl -X POST https://api.commercebackend.com/v1/search \
-H "authorization: Bearer <demo buyer api key>" \
-H "content-type: application/json" \
-H "x-request-id: sandbox-search-001" \
-d '{"query":"devkit"}'
Stripe test-mode reminder
Limits and safety boundaries
- Demo data is seeded and may reset.
- Requests are rate limited per IP (health and the Stripe webhook are exempt).
- Approval-required checkouts should not create a Stripe session before approval.
- Agent keys should be treated as demo credentials, not durable identities.
- Real merchant onboarding and payouts are out of scope.
Self-host this backend
CommerceBackend ships a production container image that runs on Cloud Run, Railway, Fly, or any container platform. It applies database migrations on boot and can seed the same deterministic sandbox fixtures used above.
docker build -t commercebackend-api .
docker compose -f infra/docker-compose.app.yml up --build
See the deploy runbook for the Cloud Run and Railway paths, required environment and secrets, and the launch checklist.