PERMISSION/PROTOCOL

Platforms

Authorization and receipts for agent platforms.

Add policy checks, human approval, and signed receipts before your agents execute high-risk actions.

Enterprise buyer question

“Who authorized this agent action, under what policy, and where is the proof?”

Permission Protocol gives platforms that answer.

Problem

Agents can act. Enterprises need authority before they act.

Your agents can call tools, update systems, send messages, create PRs, modify data, or trigger workflows. Enterprise buyers need control before those actions execute and evidence after they complete.

How it works

Policy, signature, receipt.

01

Agent requests action

02

Permission Protocol checks policy

03

Low-risk actions proceed

04

High-risk actions require human signature

05

Signed receipt is issued

06

Action executes or remains blocked

Example actions

Use it where agent actions become consequential.

Send external email
Update CRM record
Issue refund
Change billing config
Run migration
Deploy to production
Modify GitHub PR or workflow

Integration modes

External approval and receipt layer for agent products.

Embedded approval layer

Add human approval steps inside your agent product before consequential actions execute.

External signer / receipt service

Use Permission Protocol as the system of record for who authorized what and under which policy.

API / SDK integration

Call an external authorization layer from agent tools, workflows, and product backends.

GitHub Deploy Gate example

Start from the concrete GitHub adapter: required checks, human signatures, and approval receipts.

Policy checks

Decide which actions can proceed automatically and which require explicit human authority.

Human approval

Route high-risk action requests to a signer before the agent continues.

Signed receipts

Keep evidence of who authorized the action, what policy applied, and what request was approved.

Why platforms care

Enterprise customers ask for proof.

Enterprise customers do not only ask whether your agent can act. They ask who authorized the action, what policy allowed it, and what evidence exists afterward.

Add authorization evidence before agent actions execute.

Start with a concrete integration conversation. Use Deploy Gate as the reference implementation.