Off by default, scoped on purpose
- The API is off until you turn it on in Settings. Nothing listens before that.
- Each API key is scoped: decide which bots and which actions a key may use. A key for one reporting bot cannot touch your others.
- Every call is written to an audit log — time, key name, action, result — so you can see exactly what your tools and assistants did.
- Revoke a key and it stops working immediately.
MCP tools for AI assistants
The same surface is exposed as MCP tools, so an AI assistant you already use can be given a bot to run: ask it to start tonight's price check, read the results when it finishes, and summarise them — while the assistant only ever sees the bots and actions your key allows.
Approvals still apply: if a bot or flow contains an Approve step, a person has to say yes, whoever started the run.
What the API can do
- List bots and flows, with their inputs
- Start a run with input values, and stop a run
- Read run status and the results a run saved
- Check schedules and upcoming runs
Full endpoint documentation — local and cloud — is in the API docs.

