For developers

One API, every surface

GraphQL over HTTPS: 1,085 operations — 395 reads and 690 writes — on one schema. The back office, the browser register, the command line and the AI assistants are consumers of it; nothing is screen-only.

the API reference

The reference, generated from the schema

132 record types rostered, each with its operations, its types and its errors on its own pages. The schema itself is served as a file, the errors are catalogued, and there is an index written for AI assistants.

the schema itself · the error catalogue · the index written for AI assistants

Keys and sessions

An API key is minted by an owner with a scope written as rows — the service, the action, allow or disallow — and it expires on a date the owner chose. The secret shows once; your code exchanges it for a session token and never sends it again. People sign in to sessions; tills run on device sessions.

Let an app or your accountant integrate · the guides

Your first call and the envelope

Every request and answer carries a small envelope: the version you wrote against and the version that served you, the call's own id, what the call cost. Paging is a cursor grammar; errors come in one grammar with the retries named; the rate limits are documented, not discovered.

the guides

Dry runs

A write can be rehearsed: every check runs, the write is rehearsed against your current records, and nothing is stored. Ask with one flag beside the version; the answer is what the real call would answer, marked as a rehearsal.

the guides

Webhooks

Subscribe an https endpoint to the events you pick; every delivery is signed with a secret you hold, arrives at least once, and carries the record's id and revision — never its contents. Read the record back through the same API, so what your receiver stores is always the truth.

Send events to another system (webhooks)

The command line

1,085 operations, from the same registry — the command line is a consumer of the API like every other surface, so a script can do what the office does, and nothing is screen-only.

AI assistants over MCP

17 tools and 6 resources and resource templates, read-first, with only the permissions the merchant assigns. The assistant signs in over OAuth as a person, or rides an API key; the merchant connects it with one press in the office, or one command in a coding agent.

Connect your AI assistant

The agent channel

A buyer's AI agent can find your shop, search the catalog and complete a checkout over an open standard. Your side is a set of ordinary operations of this API: create the channel, publish it, pause and resume it, retire it.

Let AI shopping agents buy from you

Search, feeds and exports

One word finds the records that carry it, every kind at once, only the kinds your key may read. A question becomes a plan you can read, run while you wait or as a job. Scheduled data feeds carry your records to a BI tool; the export is machine-readable and whole.

Schedule a data feed for your BI tool · the use cases

What it costs to build on

The kernels meter: 100 million kernels are included inside the $15 a month the merchant already pays, and every call is metered and shown to them in their own ledger — the envelope on every answer says what the call cost.

the pricing page

Next steps

Read the reference, mint a key with an owner, make the first call. Then apply with the merchant — no card, no fee.

the developer documentation · Start your evaluation