Skip to main content
Merchkit is an AI-native PIM (Product Information Management) system. The API and MCP server let you operate your catalog programmatically — from your own backend, a script, or an AI agent such as Claude — over the same data your team works with in the Merchkit app.
The examples below use https://www.merchkit.com as the base URL.

​
The mental model

A few concepts carry the whole API. Internalize these and the rest follows.
1

A product is the core object

The product is the central resource. (Assets, vendors, and categories are modeled the same way and live alongside it.) When you talk to a person about a product, identify it by its primary attribute — usually its SKU. When you call the API, identify it by its UUID id.
2

Attributes are dynamic

A product’s fields are attributes, defined per workspace rather than hard-coded. Attribute definitions describe what a product can hold; attribute values are what a given product holds. To enrich a product you set attribute values — you never recreate the product to change a field.
3

Completeness is per-channel

Attributes can be channel-scoped, so completeness is evaluated per channel. The same product can be complete for one channel and incomplete for another. Whenever you check completeness, you pass the channel you care about.
Channels are read-only and global in the API — you read the available channel catalog, but you cannot create channels through the API.

​
Base URL and spec

​
Base URL
string
https://www.merchkit.com/api/v1 — all REST endpoints live under the /api/v1 prefix.
​
OpenAPI spec
string
https://www.merchkit.com/api/v1/openapi — the machine-readable contract. Field and enum descriptions are rich enough for an agent to route by semantic search, and the spec backs the API Reference in these docs.
​
llms.txt
string
https://www.merchkit.com/llms.txt — a curated, instruction-bearing guide written for agents. It lists the preferred endpoints, the filter DSL, and the common footguns. If you are pointing an agent at Merchkit, give it this URL.

​
Authentication, in one line

Every request carries your workspace API key as a bearer token: 
Authorization: Bearer mk_live_...
One key maps to exactly one workspace, and keys carry scopes. See Authentication for the full model.

​
Where to go next

Authentication

API keys, scopes, and read vs write access.

Conventions

Pagination, the filter DSL, the error envelope, and async jobs.

MCP server

Operate your catalog from Claude and other agents.

API Reference

The full endpoint reference, generated from the OpenAPI spec.