Priya is the CTO of a nine-person devtools startup, and the assistant inside her product is a feature, not a side project. She does not want to operate a vector database, a credential vault, a prompt-versioning scheme, and an audit log just to ship it — but she also refuses a black box she cannot inspect when something is weird.
Botmanor's answer is that the platform is the API. Everything the Botmanor UI does goes through the platform API, and her backend gets the same surface: create agents, publish versions, run chat, read executions. Her product authenticates with a machine credential that passes through the same enforced RBAC as a human user, scoped to her workspace. No shadow auth path, no shared admin key.
She brings her own model stack. Her Groq and Together accounts register as providers with vaulted keys — both expose OpenAI-compatible endpoints, which is the execution path Botmanor speaks natively today — and a connection test verifies each before an agent ever depends on it. When a cheaper model clears her quality bar, she changes the agent's model binding and publishes a new version with a changelog; if quality dips, she rolls back.
Iteration runs through prompt templates and the chat-test loop: render a template with variables, bind it, send test messages, and read the execution record behind every reply. The same execution records power her runway math — per-run token counts and cost, per-agent statistics — so "what does the assistant cost per active user" is a query, not a spreadsheet estimate.
The extension layers are registries she designs against today: MCP connections catalogue the tools her agents will use, and the A2A registry sketches the multi-agent pipeline she wants next — with live in-chat tool calls and delegation arriving in the runtime roadmap, on a topology she has already governed.
This story is API-first by definition: the interactive journey would happen in your own backend code rather than by clicking through the Botmanor web UI, so it is presented here as a narrative pattern rather than a clickable "Do it yourself" section.
Ready to make this your story?
