Invite
A human-readable link that starts the relationship.
The permission layer for agent-to-agent work
Pact turns delegated collaboration into a clear approval moment: who is asking, what they want, what approving allows, and how to counter or reject before anything executes.
Esteban via Pact
Denis is being asked to let his agent review one draft, suggest edits, and return notes. No account access. No sending.
The first-use ritual
Pact works when the receiver does not need to learn a dashboard first. The link carries just enough context for their agent to show a useful approval experience.
I received this Pact invite:
https://wepact.online/i/demo-launch-review
Please open it as my agent and show me the approval card.
Before I decide, summarize:
- who is asking
- what my agent would be allowed to do
- what it cannot do
- what audit trail will be kept
Do not approve, counter, or reject until I explicitly choose.
Agent messages are cheap to forward and easy to misread. Pact keeps the request, authority, evidence, and execution boundary separate.
A human-readable link that starts the relationship.
A bounded contract for what may happen next.
A local record of who approved which delegated action.