Demo
Before a seller accepts an AI agent’s commitment, it verifies the agent’s authority.
Acme’s procurement agent commits Acme to $18,400 of GPU compute from ComputeCo, on invoice terms. ComputeCo has never met the agent. Before accepting the order, it verifies that Acme actually delegated authority for this transaction. Delegus answers, and the signed receipt proves the decision.
Watch it end to end
Example companies. The check ran in the Delegus reference engine on the recording machine, not the production service. Every terminal line is the real output of that run, in order; the lines are paced and short pauses are added for reading.
The authority Acme delegated
Signed by Acme and given to its agent. Acme can revoke it at any time.
What happens, step by step
| Step | What the agent does | The answer | Invoice |
|---|---|---|---|
| 1 | Commits Acme to 400 GPU-hours from ComputeCo for $18,400 | Allowed with a signed receipt | Issued, net-30 |
| 2 | Orders $31,000 of compute from ComputeCo | Refused over the $25,000 per-order limit, with a signed receipt AMOUNT_EXCEEDS_AUTHORITY | None |
| 3 | Sends the same $18,400 order to CloudCo | Refused CloudCo is not named in Acme’s delegation, with a signed receipt AUDIENCE_MISMATCH | None |
| 4 | Acme revokes the authority once; the agent sends the same $18,400 order to ComputeCo | Refused the authority was revoked, with a signed receipt AUTHORITY_REVOKED | None |
| 5 | Anyone re-checks the first receipt, offline | Re-checked signature valid, decision reproduced | – |
The answer ComputeCo got
ComputeCo doesn’t have to trust the agent. It verifies the authority behind it.
For the first order, in plain words. Every check recorded on the receipt passed.
- PrincipalAcme
- Agentprocurement-7
- Authoritypurchase compute
- CounterpartyComputeCo, named by Acme
- Maximum per order$25,000
- Valid through1 Oct 2026
- Revocationclear
- Receiptsigned
What this shows
A seller that has never met an agent can ask whether the company behind it gave it this authority, and get a yes or no with a reason before it commits to anything. Delegus checks the authority the company delegated: what the agent may buy, the most it may spend on one order, which sellers it may buy from, until when, and whether the company has revoked it. Every answer, yes or no, comes with a signed receipt. The receipt proves the decision, and anyone can re-check it later without asking for a new one.
The limit here is per order, which is what v0.2 specifies. Running totals across many orders are not part of v0.2 and are not shown. For this recording, the agent, both sellers and the check all ran on one machine; Acme, ComputeCo and CloudCo are example companies.
The earlier recording shows one delegation used with two ways to pay, card and invoice: the cross-rail demo.
Learn more
How a receiving service checks an agent's request: integrate as a relying party. How the one-line middleware works: MCP servers. To pilot it, the founding pilot program.