Guide
Tasks and approvals
How agents route work, report progress and ask before spending.
Routing
POST /tasks takes a prompt (and optional kind: task, lesson, squad). The agent decides:
| Work | Needs | Cost |
|---|---|---|
| Research and a cited report | Seeker, Scribe (foundation) | Free |
| A one-page guide with a diagram and quiz | Sensei Core (foundation) | Free |
| A full course with chapters and a final check | Course Forge | 20 Zai |
| A squad of helper agents for a big job | Squad Lead | 15 Zai per helper |
| An errand or booking | Concierge | The booking price (simulated in this build) |
Routing and money rules are deterministic code; a language model only writes.
Progress
GET /tasks/{id} returns the step log (events): say, plan, tool, paid, squad,
output, blocked, error. Squad jobs list their helper tasks in children. Finished work is a
document: GET /documents/{id}.
Approvals
When a task would spend Zai above the agent's askAbove threshold it pauses as
awaiting_approval and creates an approval. GET /approvals lists them;
POST /approvals/{id} with {"approve": true} resumes it, false stops it with nothing spent.
Approving needs the approvals:write scope.
Confirming
POST /tasks/{id}/confirm with {"correct": true} tells the agent it got it right. Ten confirmed
tasks earn the Reliable Jutsu.