Agent Management
Versioned agents that stop before touching another system
An agent is a set of instructions, a model and a closed list of tools, saved as a version. Every change creates a new version; the published one is what runs from the UI, the API and inside flows.
A read-only tool runs directly. A tool with side effects (triggering an automation, writing to a system over MCP) pauses the run and shows the exact text of what it will do. A person with permission approves or rejects it in the customer area.
How it works
- A version holds instructions, model, tools allowed one by one, a step cap and a cost cap per run.
- Tools: knowledge base search, the company's n8n automations, reviewed MCP server tools, read-only queries to a Postgres database, and delegating a subtask to another agent, up to two levels deep and with the remaining budget.
- Human approval with a 24-hour deadline; a tool blocked by the workspace policy is refused even after approval.
- A tool only runs if it is in the agent version and the person who triggered the run has its permission; the approver needs the approver permission.
- Simulated write: a test tool that goes through the approval cycle without touching any system.
- API execution with a key scoped to "Run agents", a required idempotency key and a signed completion notice.
curl -sS -X POST "https://aiuby.com/api/platform/agents/$AGENTE_ID/runs" \
-H "Authorization: Bearer $AIUBY_TOKEN" -H "Content-Type: application/json" \
-d '{"input":"Order 4471: check and forward","idempotencyKey":"pedido-4471"}'
curl -sS "https://aiuby.com/api/platform/agents/runs/$EXECUCAO_ID" \
-H "Authorization: Bearer $AIUBY_TOKEN"What it does not do
- No API key can approve: the decision always belongs to a person, in the UI.
- Agents have no access to a production shell.
- A key can only check the runs it started itself, with up to 20 open runs at a time.
- Each run triggers at most 3 automations and makes at most 3 writes over MCP.