Connect the principal.
Establish the person or organization represented by the agent, and the delegation that connects them.
Agent trust · In development
An agent can act quickly. Its authority should be just as clear: who it represents, what it may do, and when a person needs to approve.
The model
Establish the person or organization represented by the agent, and the delegation that connects them.
Describe the resource, operation, and constraints. Permission to request a refund is different from permission to execute one.
Amounts, expiry, resource limits, and human approval requirements determine when an action needs another decision.
Keep the request, relevant authority, policy decision, and actual execution result distinguishable in the record.
A concrete example
Consider a support agent with permission to execute refunds up to $200 while its delegation remains valid.
| Request | Delegation | Policy outcome |
|---|---|---|
| Refund $80 | Valid | Within the amount limit; other business checks still apply. |
| Refund $800 | Valid | Requires additional approval. |
| Refund $80 | Expired | Cannot proceed under this delegation. |
Our focus
Agent trust is in development. We start with one consequential action and the identity and policy systems you already run.
Read our approachCommon questions
No. Recognizing automated behavior does not establish who delegated an action or whether the requested action is permitted.
No. Identity and authorization answer different questions. The action still needs to fit the relevant scope, constraints, and current policy.
When an agent uses submitted material to propose an action, the workflow may need both a review of the evidence and a check of the agent’s authority.
Agent trust
Bring your agent workflow and the boundaries it needs to respect.
Book a demo