Getting access — API & SDKs
What's real today, stated plainly — the same honesty standard as Security & Trust.
The REST API is live today
Every capability documented across these pages is a real, gateway-routed REST API running against the live platform — not a roadmap item. It's what MergeMind Commerce itself runs on, and what powered the real order in Case Study #001. API access, OpenAPI specs and a sandbox tenant are provided during onboarding.
Typed SDKs
A set of typed TypeScript SDK packages wraps the REST surface — a core client plus per-domain packages (auth, billing, tenancy, and more). They exist and are used internally today; they're shared with you as part of onboarding rather than being on a public package registry yet.
// Illustrative — the shape of the API once you have access,
// not a package you can npm install today.
const tenant = await platform.tenants.create({ name: 'Acme Inc' });
await platform.auth.invite({
tenantId: tenant.id,
email: 'admin@acme.com',
role: 'TENANT_ADMIN',
});
// Reads and writes are automatically scoped to the caller's tenant.
const invoices = await platform.billing.invoices.list({ status: 'OPEN' });A public release of the SDK packages is planned. We'd rather ship it once it's genuinely ready — real package metadata, real documentation per package, a license decision made deliberately — than publish something today that looks done and isn't.
Want in now? Request developer access and we'll get you the packages, OpenAPI specs and a sandbox tenant directly — you don't need to wait for the public release to start building.