Build with AI
Use AI coding agents to build Kentro integrations, with docs, prompts, skills and MCP servers made for them.
AI coding agents such as Claude Code, Codex and Cursor can build most Kentro integrations from one request, as long as they read current Kentro docs and follow Kentro's rules. This category gives them both. It also shows how to connect an AI assistant to your own Kentro workspace.
What an agent can build on Kentro
| Project | API | A request that works |
|---|---|---|
| Marketplace or shopping cart connector | Channel API | "Import our marketplace orders into Kentro and send tracking back." |
| ERP or accounting sync | Channel API | "Sync customers, invoices and payments between Kentro and our ERP." |
| Warehouse or 3PL integration | Channel API | "Send Kentro fulfillment orders to our WMS and report what shipped." |
| Retailer purchase orders | Channel API | "Create retailer POs in Kentro from our EDI files, then accept them." |
| Custom storefront | Store API | "Build a Next.js storefront on our Kentro catalog, cart and checkout." |
| Website and server measurement | Kentro Pixel | "Install Kentro Pixel with our consent banner and send paid orders from the backend." |
With Kentro MCP, an assistant also works inside your workspace as you: it answers questions about orders, inventory and fulfillment and runs Kentro Assistant tasks. See Kentro MCP.
The three building blocks
1. Docs for agents
Every page on this site has a Markdown version, https://docs.kentro.io/llms.txt maps the whole site, and the AI menu on each guide page sends the page to ChatGPT or Claude. See Docs for agents.
2. Prompts and skills
- Prompt library: requests to paste into an agent, one per project type. Each one names the docs to read, the inputs to ask for, the rules to follow and the checks to run before the agent reports done.
- Instructions for AI agents: the rules every Kentro integration follows (which API for which job, credentials, idempotency, money, pagination, errors), written for an agent to follow word for word.
- Agent skills: the same rules packaged as skill files for Claude Code, as
AGENTS.mdsections for Codex and as Cursor rules.
3. Kentro MCP
A remote MCP server that connects Claude, Claude Code or Codex to Kentro Assistant. A connection signs in through Kentro and acts with your permissions, nothing more. See Kentro MCP.
I want to...
| I want to | Start with |
|---|---|
| Connect a marketplace or shopping cart | The channel-connector prompt in the prompt library, plus the kentro-channel-api skill |
| Sync an ERP or accounting system | The erp-sync prompt, plus the kentro-channel-api skill |
| Connect a warehouse or 3PL | The wms-3pl prompt, plus the kentro-channel-api skill |
| Bring retailer purchase orders into Kentro | The retailer-edi prompt, plus the kentro-channel-api skill |
| Build a custom storefront | The custom-storefront prompt, plus the kentro-store-api skill |
| Install Kentro Pixel on a website | The pixel-web prompt, plus the kentro-pixel skill |
| Send orders and refunds to Kentro Pixel from a backend | The pixel-server prompt, plus the kentro-pixel skill |
| Give a coding agent current Kentro docs | Docs for agents |
| Ask an AI assistant about the workspace's orders, stock or fulfillment | Kentro MCP |
How a build session goes
- Give the agent the docs: tell it to read
https://docs.kentro.io/llms.txt(see Docs for agents). - Install the agent skills, or add Instructions for AI agents to the agent's rules.
- Paste the prompt for your project from the prompt library.
- When the agent asks, create a sandbox API key in Kentro OS at
https://kentro.ccunderUsers>API keys(see API keys), put it in environment variables and answer the agent's questions. - Let the agent build against the sandbox (
https://apis.kentro.dev) and run the acceptance checks the prompt lists. - Review the code and the check results, then follow Go live to switch to a production key.
There is no Kentro SDK or CLI
Kentro's APIs are HTTPS and JSON, called with any HTTP client. An agent that installs a package such as
kentro-sdkor runs akentrocommand is guessing; point it to Instructions for AI agents. The one script Kentro serves is the Kentro Pixel browser SDK athttps://pixel.kentro.live/sdk/v1/kentro-pixel.js, loaded with a script tag.
Kentro MCP is not for building integrations
Kentro MCP (
https://apis.kentro.live/kiq/v1/copilot/mcp) serves your workspace data through Kentro Assistant and needs a Kentro sign-in. An agent that builds an integration reads the docs and calls the APIs with an API key; it never goes through Kentro MCP.
Related
Updated about 12 hours ago