Agent Specification
In short: a Tajo agent is a role in your workspace with instructions, a fixed list of tools and optional skills. Each tool has a permission tier. The tier, not the agent, decides whether a call runs, waits for your approval, or is refused.
The parts of an agent
| Part | What it is |
|---|---|
| Name and role | What the agent is called and the role slug it runs as. The 15 built-in roles are reserved. |
| Instructions | The prompt the agent works from. |
| Tools | The only actions the agent can take. An agent cannot call a tool that is not on its list. |
| Skills | Written guidance the agent loads, such as email-craft or compliance-reviewer. A skill adds knowledge, never a new action. |
| Budget | An optional monthly spend cap. |
| Routines | Requests that run the agent again on a schedule. |
There is no agent file format. You create and edit agents in the app.
Permission tiers
Every call an agent makes goes through one check before it runs. The check stops everything when the workspace is paused or over its hard budget limit. Otherwise the tool’s tier decides:
| Tier | What happens | Examples |
|---|---|---|
| Allowed | The call goes ahead | Checking a draft for compliance, drafting a template, computing a segment, running active syncs |
| Needs a standing grant | Runs only if you granted this agent that tool; otherwise it asks you | Capturing a screenshot of a web page |
| Needs approval | The run pauses until you approve this exact call | Scheduling a send |
An approval covers the exact input you saw. If the agent changes one field after you approve, the approval no longer matches and the call waits again.
Gates that hold whatever the tier
- Publishing a sync. The Brevo Integration Architect activates a sync rule only with the approval you gave for it. A request expires after 30 minutes.
- Consent before data moves. A sync that writes contacts or events to Brevo cannot be published unless it filters on consent and suppression.
- Consent before a message goes out. A marketing send needs an opt-in on the channel it uses. Unknown means no send.
- Large sends. Any send to 50 or more contacts waits for approval.
Routines
A request on the home screen with a schedule in it, such as “every Monday”, becomes a routine that runs the same agent again. Schedule words map to fixed times in UTC; the table is in Tajo 101. Routines started by an event, such as a new order, are not built yet.
The built-in roles
| Role | Main tools |
|---|---|
| Brevo Integration Architect | Inspect the source, sample records, propose and validate a field map, dry-run, save a draft, request publish approval, activate with that approval |
| Sync Operator | Run active sync rules |
| Segment Builder | Compute a segment |
| Compliance Reviewer | Check a send for compliance, request approval |
| Engagement Designer | Draft campaigns and templates, check a draft’s output, request approval |
| Performance Analyst | Analyse workspace performance, compute a segment, draft a campaign, request approval |
| Orchestrator | Draft campaigns and templates, compute segments, request approval, schedule a send |
What each one never does: Tajo agents.