Aisle / Developer documentation

Trust starts with clarity.

What the sandbox does, what it does not do, and what must be supplied before live commerce.

Launch information pending. This page is a status disclosure, not published terms of service, a privacy policy or a compliance certification.

Current boundaries

The backend runs on Supabase Edge Functions and private Postgres, reached through a Cloudflare gateway. Sandbox access uses scoped bearer credentials. Spending authorization uses a separate approver credential; guest PAP is read-only. Real supplier writes and purchasing are disabled in code. These controls have sandbox tests; they do not establish production readiness.

Legal & merchant details

Data in this site

The landing page has no account, checkout, credential input, inquiry form or analytics script. The copy buttons use your browser clipboard only when clicked. Hosting infrastructure processes web requests and may retain request logs; the operator’s detailed privacy and retention disclosures remain pending. Use fixture data when exercising the sandbox API.

Before real orders

Aisle needs a verified seller, authorized catalog rights, live supplier connections, approved payment processing, authoritative tax and shipping calculations, production identity and consent, operational monitoring, and tested order/payment reconciliation. None of the named platforms or protocols implies approval to transact.

Sandbox cancellation and return requests do not promise a shipment, refund, return label or RMA approval. No security audit, certification, platform endorsement or supplier partnership is claimed.

Platform names

Meta Muse, Instinct, Grok Bot, ChatGPT Dots, Gemini and independent MCP agents describe the intended audience. They are not a list of confirmed integrations, endorsements, approved clients or compatibility certifications.