Hosted sandbox · Stripe test mode only
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://commercebackend-sandbox.vercel.app
Health: https://commercebackend-sandbox.vercel.app/healthMinimal request shape
Authorization: Bearer <demo buyer api key>
Content-Type: application/json
X-Request-Id: sandbox-demo-001Fastest 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 stateExample calls
curl https://commercebackend-sandbox.vercel.app/health
curl -X POST https://commercebackend-sandbox.vercel.app/v1/public/search \
-H "content-type: application/json" \
-H "x-request-id: sandbox-search-001" \
-d '{"query":"devkit"}'Stripe test-mode reminder
Test mode only.
Never enter a real payment card in the sandbox. Use Stripe’s published test cards and assume all sandbox checkout flows are non-production.
Limits and safety boundaries
- Demo data is seeded and may reset.
- Write endpoints may be rate limited.
- 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.