Skip to content
Ratify Protocol™
Try it

Build with Ratify Protocol

Open-source alpha · 1.0.0-alpha.16 · 79 conformance fixtures

Ratify lets a receiving system verify whether an agent was delegated authority for a specific action. The principal signs the delegation, the agent presents it, and the receiver verifies it before execution.

The integration boundary

Put Ratify immediately before a consequential tool call, API request, payment, workflow transition, or physical action. Your application remains responsible for local policy, resource context, and execution. Ratify returns the authority decision that your application can enforce.

What developers implement

  1. Issue a bounded delegation for an agent public key.
  2. Carry the delegation and a verifier challenge with the action.
  3. Verify the chain, scope, constraints, validity, freshness, and revocation state.
  4. Execute only after the receiving application gets an allow decision.

Reference implementations

Reference SDKs are available in Go, TypeScript, Python, Rust, and C/C++. Implementations share the canonical signing bytes and expected verdicts in the conformance fixtures, so an implementation can be checked against the same wire behavior as the reference.

Start with the developer documentation, inspect the source repository, or read the pinned protocol specification.

Keep the receiver in control

Ratify does not decide whether an action is wise, safe, compliant, or useful. It verifies delegated authority against the context supplied by the receiver. Keep business policy, resource authorization, fraud controls, and tool validation in your application.