API resources
POST /v1/agentsPOST /v1/runsGET /v1/runs/{run_id}/messagesPOST /v1/runs/{run_id}/human-requests/{request_id}/respondDuvo gives developers the operating layer around agent work: queues, tools, approvals, files, multi-agent routing, observability, and programmatic control.
Trigger
Start work from code, a webhook, the CLI, a schedule, or MCP.
01API / CLI / MCP
Queue
Cases wait, retry, and dispatch without losing state.
02Durable intake
Assignment
The prompt, tools, SOPs, files, and connections run as a build.
03Versioned worker
Handover
Subagents and configured targets take over the parts they own.
04Specialists
Gate
Risky decisions pause with full context before execution continues.
05Human approval
Done
The result, files, messages, tool calls, and audit trail stay attached.
06Completed case
Connection patterns
Duvo does not assume every system has a clean API. Agent work can mix hosted connections, browser control, custom MCP, remote desktop, and event or file intake in the same assignment.
Connection path
Use managed OAuth/API connections for common business systems and keep credentials out of one-off agent code.
Platform primitives
Use Duvo when your agent needs to run inside a real operating model: assigned work, durable intake, controlled tools, human decisions, and visible outcomes.
Ship versioned workers with prompts, SOPs, tools, connections, evaluation notes, and release history instead of one-off scripts.
Start, inspect, pause, resume, approve, and replay agent work from your app, backend service, or operator workflow.
Build intake for claims, invoices, tickets, alerts, leads, or files so assignments can claim and process work at controlled concurrency.
Pause for approvals, missing context, policy decisions, or exception review without breaking the run or losing state.
Stage evidence, generated artifacts, browser downloads, and temporary execution state alongside the run that produced them.
Use hosted tools, your own MCP servers, enterprise APIs, browser automation, and desktop access through one controlled runtime.
Run work on events, files, webhooks, queues, or cadences without turning every use case into custom orchestration code.
Package reusable capabilities so teams can share specialist behavior across assignments without copying prompts by hand.
Queue state
Retries
Tool auth
File staging
Schedules
Webhooks
Handover
Approvals
API, CLI, MCP control
Developers can start runs, create cases, respond to human gates, connect MCP tools, and inspect run messages without treating Duvo as a black box.
API resources
POST /v1/agentsPOST /v1/runsGET /v1/runs/{run_id}/messagesPOST /v1/runs/{run_id}/human-requests/{request_id}/respondCLI commands
duvo runs start --agent <agent-id> --jsonduvo runs respond <run-id> --approveduvo cases bulk-delegate ...Docs and MCP
CLIAPI referenceHosted MCPCustom MCPMulti-agent systems
Duvo lets a parent assignment route work to specialist assignments, queue-backed consumers, or configured handover targets while the run history stays connected.
subAgents
A parent assignment can create specialist assignments with their own SOPs, tools, connections, files, and completion criteria.
Handover
When the run discovers a dispute, missing evidence, or approval path, it can hand work to the assignment configured to own that next step.
Queue-backed specialists
A producer creates cases, triage assigns priority, specialist consumers process them, and humans only handle exception gates.