Documentation.

Everything you need to build on Sparx — the modular content and commerce OS. Sparx is API-first: every feature is an endpoint before it's a screen, and a native MCP server lets AI agents read and write live business data.

Start here

New to Sparx? The Quickstart takes you from zero to a live API call in about ten minutes. Then explore by area:

Quickstart →
Create a key, make your first request, and subscribe to an event.
API reference →
Every REST and GraphQL endpoint, with request and response examples.
SDKs →
Typed clients for TypeScript, plus the headless Builder SDK.
MCP server →
Give AI agents direct, governed access to your tenant’s data.

How Sparx is built

A few platform commitments shape every page in these docs:

  • API-first. The dashboard, the storefront, and AI agents are all consumers of the same REST + GraphQL surface. Anything the UI can do, your code can do.
  • Modular and feature-flagged. A tenant activates only the modules it uses — content, commerce, CRM, CMS, email, B2B, dropship, AI. Disabled modules return a clear error and store no data.
  • Event-driven. Writes emit events (webhooks and Pub/Sub); side effects run in workers, never inline.
  • Multi-tenant by default. Every API key is tenant-scoped and isolated by PostgreSQL Row-Level Security — a key can never reach another tenant’s data.