How Distri fits your stack
Most agent platforms ask you to move the work to them: a sandbox, a new chat surface, a second set of APIs. Distri works through the product you have. Layer by layer, this is what stays yours and what Distri adds.
| Layer | Stays yours | Distri adds |
|---|---|---|
| Screens and state | Your web or mobile app, as it is | Chat components, and client-side tools that call your own functions |
| Auth and permissions | Your login and the user’s session | Tools run inside that session, so the agent can do what the user can do |
| APIs and data | Your backend, plus the MCP servers you already expose | Remote MCP tools, filtered per agent |
| Models | Your provider accounts and keys | A model per agent, with cost and limits per end user |
| Channels and operations | The chat apps and internal tools your team uses | Bots, workflows, webhooks and an API for the same agents |
Related
- Embedded agents: client-side tools, in detail.
- Channels: bots on Telegram, Slack, WhatsApp and Discord.
- Usage tracking: cost and limits per end user.