Developer documentation

Build on a multi-tenant commerce platform — one GraphQL API, a Liquid storefront engine, and an MCP server for AI agents.

Next Architecture

Welcome to the developer documentation. This platform runs many independent stores (shops and content sites) on shared infrastructure, exposes everything through a single GraphQL API, renders storefronts with a Liquid theme engine, and ships a Model Context Protocol (MCP) server so AI agents can build and operate stores end-to-end.

Where to start

New here? Read Architecture and Core concepts for the mental model, then Create a store.
Integrating? Grab an API key and open the API reference (try requests live in the Explorer).
Using an AI agent? Jump to MCP overview and Connect for Claude Code, Cursor, Claude Desktop and more.

What you can build

One API, every surface

Everything the admin UI can do is available over the GraphQL API, scoped by your API key. The storefront, POS, and integrations all speak the same schema.

Storefronts — catalog, cart, checkout, customizable Liquid themes.
Content sites — brochure/listing/blog sites with no cart (commerce toggled off).
Catalog — EAV products with custom attributes, configurable/bundle variants, collections.
Operations — orders, customers, loyalty, inventory, marketing rules, payments.
Automation — drive any of the above from an AI agent via the MCP server.

Conventions in these docs

Code blocks are copy-ready; hover to reveal the copy button.
crmk_… denotes an organization API key.
Type references in the API reference link to their definitions — click through to explore.