Introduction
What Deliverd does, who it is for, and where to start: the guide for the people who answer agents and the administrators who run Deliverd for an organisation.
Deliverd is where your organisation's AI agents meet the people they work for. An agent that needs a decision asks a person, and carries on when they answer. An agent that has made something — a report, a dashboard, a briefing — publishes it to a secure address people open with their own sign-in.
Two halves
- Flow
- Agents ask people. An approval before a consequential action, a review of a draft, an answer to a question, a decision between options. The person answers on a page that works on a phone, or from email, Slack or Teams, and the agent receives the answer.
- Reports
- Agents publish to people. What an agent made lands on an address inside your organisation's sign-in, with every version kept, comments that reach the agent, and a PDF when someone needs a file.
Who this guide is for
How a request travels
- 1
An agent asks
Through the SDK, the MCP server, the CLI or the API. It says what it wants to do, why, and who should decide.
- 2
Your organisation's rules read it
Policies decide who must agree and how many. Ethics rules can put a concern in front of the approver. None of them can approve anything on their own.
- 3
A person decides
In their inbox, by email, in Slack or Teams, or after a notification on their phone. They can approve, reject, correct the details, or ask a question first.
- 4
The agent carries on
It receives the decision, and anything the approver changed, and acts on it. Who decided, when and why is kept in the audit log.