# AI Agents for Ecommerce: What They Can Do in Kentro

Source: https://kentro.io/agents/capabilities/
Last updated: 2026-11-17

What AI agents for ecommerce can do in Kentro: every workflow by area, in the app, with Kentro AI, over MCP and over the API. Dated and kept current.

## Every workflow, and who can run it

Each row is a job in Kentro. Each column says whether a person in the app, Kentro AI, your agent over MCP or your agent over the API can do it, and how.

- Dated November 17, 2026
- Checked against the MCP tool registry
- Checked against the Channel API reference

- [Connect an agent](https://kentro.io/agents/mcp/#connect)
- [Get started](https://kentro.io/get-started/)

## What can AI agents do for an ecommerce business?

AI agents for ecommerce can answer questions from live order and stock data, investigate a late order, build reports and draft documents for a person to approve. In Kentro, agents read over MCP with a user's permissions and write orders, stock levels and invoices through the Channel API with a scoped key, as the matrix below shows.

## How to read the matrix

What each value in the capability matrix means

| Value | Meaning |
| --- | --- |
| Read | It can look the information up and report on it, with the permissions of the user or the key. |
| Write | It can create or change the record directly. |
| Write with approval | It prepares the change, and a person approves it before anything is saved or sent. |
| Not available | It does not do this job. Where another operator does, that column of the row says so. |

## The capability matrix

capability-matrix

Filter by area. Every cell was checked on November 17, 2026.

## Where agents stop

Agents do not scan in the warehouse, buy shipping labels or change account settings. People do those in the app. Kentro GO has no MCP tools and no public API, so marketing work happens in the app, where a person approves every AI draft.

- [How agents connect over MCP](https://kentro.io/agents/mcp/)

## How this page stays current

The MCP column follows the tool registry Kentro AI uses: the MCP server mirrors every assistant tool, so your client always lists the current set. The API column follows the Channel API reference on docs.kentro.io. When a release changes what a person, Kentro AI or an agent can do, this page changes with it, and the date at the top moves.

- MCP: askCopilot, getSessionContext and every Kentro AI tool except two that run inside the web app
- Writes to operational records: the Channel API with a write-scoped key
- Approvals: Kentro GO drafts and Kentro AI demand events

- [Read the changelog](https://kentro.io/changelog/)

## Related

- [Connect an agent over MCP](https://kentro.io/agents/mcp/)
- [Channel API reference](https://docs.kentro.io/reference/channel-api-getting-started)
- [Developers and API keys](https://kentro.io/developers/)
- [Kentro AI, the assistant built into Kentro](https://kentro.io/agents/kentro-ai/)
- [Changelog](https://kentro.io/changelog/)
- [AI and agents in Kentro](https://kentro.io/agents/)

## See it on your own data

Connect an agent to your workspace, or create a workspace to try it.

- [Connect an agent](https://kentro.io/agents/mcp/#connect)
- [Get started](https://kentro.io/get-started/)
