The permission layer for agent-to-agent work

Send a link. Let their agent understand the ask.

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.

Incoming Pact Relay verified

Esteban via Pact

Review and improve a launch email

Denis is being asked to let his agent review one draft, suggest edits, and return notes. No account access. No sending.

Can do Read one shared draft
Cannot do Send email or edit CRM
Expires In 24 hours

The first-use ritual

Paste this into your agent.

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.

Agent prompt
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.

Text can ask. Grants decide.

Agent messages are cheap to forward and easy to misread. Pact keeps the request, authority, evidence, and execution boundary separate.

01

Invite

A human-readable link that starts the relationship.

02

Grant

A bounded contract for what may happen next.

03

Audit

A local record of who approved which delegated action.