CORE FIRST
Website and accounts
Database, signup/sign-in, account security, verified catalogue and pricing, orders, wallet, settlement, support and operations are built and tested first.
ACCOUNT MARKET / EXPLORE
Developer API
The Developer API is planned for a later phase. It is not available today.
No API keys are issued yet
These pages are a plan, not a live contract. Keys, reseller endpoints and live examples arrive after the shop itself is finished. The website always uses a signed-in session, and the connection details behind each route stay on the server, never in the browser.omer keys.
Delivery order
The API comes after the customer-facing workflows it depends on.
SECURITY REVIEW
Prove the underlying flows
Ownership, idempotency, spend controls, failures, privacy, rate limits and recovery must pass before any external customer API is exposed.
LAST PHASE
Customer API and keys
Only then will the versioned API contract, user-generated keys, reseller endpoints, documentation and safe playground be designed and reviewed.
Current availability
The server does not substitute a mock response for an unconnected capability.
| Capability | State | What that means |
|---|---|---|
| User-created API keys | Not available | No key can be issued, revealed, used or recovered. |
| Customer /api/v2 business routes | Unavailable | Unconnected routes fail closed with 503; no supplier action is sent. |
| API playground | Disabled | This page sends no requests and accepts no credentials. |
| Provider credentials | Server-side only | Separate backend integration credentials; never exposed or repurposed as customer keys. |