API, CLI, MCP
Everything the console does, your agent can do too
One operations layer behind three doors: a REST API, the ciele command line, and an MCP server your coding agent connects to. The console is not a privileged client.
One implementation, three doors
A console button and an API call execute the same operation, with the same role check. Nothing is reachable from one and not the others, so an integration cannot fall behind the product.
Snippets on the page you are already on
Open the developer panel from any screen and it shows that screen's operations as CLI, cURL and MCP calls, with the ids in front of you already filled in.
Your agent connects in one line
Point Claude Code, Cursor or any MCP client at the hosted endpoint with an organization API key. Coarse tools rather than one per endpoint, so the agent picks the right one.
Scoped by the key, not by trust
A key can only do what its role allows
An API key is capped at the role of whoever minted it, and every call re-checks that role in the operations layer. Publishing and organization administration need the roles that carry them. A read-only MCP server refuses a write before the request leaves the process.
Always exploring
Curious about everything you know
Point it at your websites, documents and FAQs. It keeps digging until it can answer with a citation, and says so when it can't.
Try it on your knowledge