Build with Originary

Publish a peac.txt policy, add middleware to check requests, and return signed interaction records in response headers.

1. Deploy /.well-known/peac.txt
2. Add verification middleware
3. Return signed record headers

Install the PEAC MCP server to give AI agents five verification tools: verify, inspect, decode, issue, and bundle.

1. Install @peac/mcp-server
2. Configure in Claude Desktop or Cursor
3. Agents verify records via tool calls

Attach signed interaction records to agent-to-agent messages using the A2A metadata carrier. Verify at each hop.

1. Issue records with @peac/protocol
2. Attach via A2A metadata carrier
3. Verify at receiving agent

Validate a PEAC interaction record signature offline using the issuer's public key. No network call required.

1. Extract the PEAC-Receipt header
2. Fetch the issuer JWKS (once)
3. Call verifyLocal() with the public key

Initialize and deploy your policy to /.well-known/peac.txt

# Install CLI and init policy
npm i -g @peac/cli
peac policy init --profile api-provider

# Generate deployment files
peac policy generate --out ./public --well-known

Validate your policy file and test rule matching

# Validate policy syntax
peac policy validate peac-policy.yaml

# Explain which rule applies
peac policy explain peac-policy.yaml \
  --purpose train --type agent

# Output:
# Decision: DENY
# Matched Rule: block-training

Verify incoming PEAC-Receipt headers in your middleware

import { verifyLocal } from '@peac/protocol'
import { importJWK } from '@peac/crypto'

const key = await importJWK(jwk)
const result = await verifyLocal(receiptJws, {
  publicKey: key,
  profile: 'strict',
})

if (result.verified) {
  console.log('Valid:', result.claims)
}