Docs

Getting access — API & SDKs

What's real today, stated plainly — the same honesty standard as Security & Trust. This list is the single source for every SDK claim on the site.

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, FixerJi and White Owl run on, and what powered the real order in Case Study #001. The core services' OpenAPI reference is public: API reference. A sandbox tenant and the engine APIs (Commerce, Marketplace, Learning, Finance) are provided during onboarding.

SDKs, clients and tooling — current status

REST API

api.mergemind.co · public OpenAPI reference for the core services

Every capability — identity, tenancy, billing, authorization, events, and the Commerce, Marketplace, Learning and Finance engines — behind one gateway.

Live

TypeScript client SDK

@platform/sdk-core · sdk-auth · sdk-tenant · sdk-billing · sdk-feature · …

A core client (token refresh, tenant header, retries, idempotency keys) plus per-capability clients. FixerJi and White Owl are built on it.

Shared at onboarding

React UI kit

@platform/ui-auth · ui-account · ui-onboarding · ui-notifications · ui-billing · …

Sign-in, MFA, account, onboarding, notifications, billing and admin/tenant portal building blocks.

Shared at onboarding

Commerce SDK

@commerce/sdk-commerce · ui-storefront

Catalog, cart, checkout and admin clients, plus storefront components.

Shared at onboarding

Marketplace, Learning & Finance clients

Use the REST API today (each engine’s app ships its own typed client layer); packaged SDKs are planned.

API today · SDK planned

Android (Kotlin) SDK

sdk-core · sdk-auth · sdk-notification

Core client with secure token storage, auth and notifications implemented; the remaining modules are in progress.

Partial

React Native core

@platform/sdk-core-native

The core client with offline-aware request queueing for React Native apps.

Internal preview

Project scaffolder & AI-agent server

create-app · Commerce MCP server

A starter generator for new apps, and an MCP server that lets AI agents work with Commerce.

Internal preview

Public npm release & self-serve API keys

Public packages with per-package docs, and a console to create keys without talking to us.

Planned

What the TypeScript SDK looks like

This is not illustrative: it's the same client construction White Owl's and FixerJi's web apps use today. The packages are shared with you during onboarding rather than installed from a public registry.

real SDK usage · packages shared at onboarding

import { createApiClient, SessionStorageAdapter } from '@platform/sdk-core';
import { createTenantApi } from '@platform/sdk-tenant';
import { createBillingApi } from '@platform/sdk-billing';

const client = createApiClient({
  baseURL: 'https://api.mergemind.co/api/v1',
  tokenStorage: new SessionStorageAdapter(),
});

// Onboard a business and invite its first admin
const tenants = createTenantApi(client);
const tenant = await tenants.onboard({ tenantName: 'GreenLeaf Garden' });
await tenants.inviteUser(tenant.tenantId, { email: 'owner@greenleaf.in', role: 'TENANT_ADMIN' });

// Plans come from the same platform — no separate billing vendor
const plans = await createBillingApi(client).listPlans({ status: 'ACTIVE' });

Why not on npm yet? We'd rather publish once it's genuinely ready — real package metadata, documentation per package and a deliberate license decision — than publish something that looks finished and isn't. You don't need to wait for that to start building.

Want in now? Request developer access and we'll get you the packages, the engine APIs' OpenAPI specs and a sandbox tenant directly.

Deployment