Developers
Build on the commerce system of record
REST APIs for orders, inventory, fulfillment, invoices and storefronts, an MCP server for agents, and docs written for people and for coding agents.
- Scoped API keys
- Idempotent writes
- Production and sandbox base URLs
- llms.txt for coding agents
curl -s https://apis.kentro.live/channel/v1/channels \
-H "kentro-key: $KENTRO_KEY" \
-H "kentro-secret: $KENTRO_SECRET"What is a headless ecommerce API?
A headless ecommerce API lets you build your own storefront, app or agent on a commerce back end without using its front end. Kentro's Store API, part of Kentro Storefront, covers buyer sign-in, the catalog at each buyer's prices, cart, quotes and checkout. The Channel API moves orders, stock, shipments and invoices in and out of Kentro.
APIs
Three REST APIs and an MCP server
One workspace, one set of permissions, JSON in and out.
Channel API
Orders, customers, products and listings, inventory levels, fulfillment orders, shipments, invoices, payments, retailer purchase orders and vendors. For marketplaces, carts, EDI, 3PLs and ERPs.
Learn moreStore API
Buyer sign-in, the catalog at each buyer's prices, cart, quotes, checkout, orders, invoices, account and subscriptions, for a storefront you build yourself.
Learn morePixel API
A browser SDK and a server events API for site events, sent on to the ad platforms and destinations you connect.
Learn moreMCP server
Assistants sign in as a user and use Kentro AI and its read tools with that user's permissions.
Learn more
Keys and conventions
API keys, scopes and safe retries
Admins create keys in Kentro OS under Users, API keys. A key belongs to one workspace and carries the scopes of the permission groups you assign: channel:read for reporting, channel:write for a full integration. A key can be bound to chosen sales channels.
Send the key and secret as the kentro-key and kentro-secret headers, or exchange them for a short-lived bearer token. Every write takes an Idempotency-Key header, so a retry replays the original answer instead of writing twice.
- Production: https://apis.kentro.live/channel
- Sandbox: https://apis.kentro.dev/channel, with its own workspaces and data
- Store API: https://apis.kentro.live/store/v1
- No webhooks on the Channel API: integrations poll with updatedSince
{
"data": [
{
"id": "64f0aabb-ccdd-1122-3344-000100000000",
"name": "Web store",
"type": "woocommerce",
"isActive": true,
"currency": "USD"
}
],
"nextCursor": null,
"limit": 50
}For coding agents
Docs your coding agent can read
Point Claude Code, Codex or your own agent at these before it writes a line of code.
docs.kentro.io/llms.txt
Every published docs page with a one-line summary and a link to its Markdown version.
Learn morekentro.io/llms.txt
What Kentro is, its products, pricing and where each page lives, written for answer engines.
Learn morePrompts and agent skills
Ready prompts for common integrations and agent skills for the Channel API, the Store API and Kentro Pixel.
Learn moreConnect a coding agent
Add the MCP server to Claude Code or Codex with one command and ask about your workspace while you build.
Learn more
Start building on Kentro
Read the docs, or create a workspace and generate your API keys.


