PLATFORM OVERVIEW

Originary
Platform

Deploy PEAC terms, enforcement, and receipts in real systems.

PEAC is the open standard for portable decision records. Originary is the production stack that helps you publish terms, enforce decisions, and return signed receipts that anyone can verify.

This page describes the platform surface; the homepage explains the standard.

Open protocol. No lock-in. Edge-ready.
Use self-hosted components, or talk to us for managed deployments.

View demoRead the spec
POLICY
/.well-known/peac.txt
📋
Policy
🔑
Access
💳
Settlement (optional)
✅
Receipt
📊
Trace
peac.txt
# AIPREF snapshot (simplified)
training: deny
rag: allow-with-attribution
commercial_use: negotiate
inference: allow
logging: minimal
policy_hash: 9f3c...c2abv2025-11-30
PEAC-Receipt ready - AIPREF-compatibleTry Declare

Deploys on

Adapters

Roadmap

How it works

Deploy policy once. Enforce anywhere. Verify outcomes independently.

1
📋

Declare

Define interaction terms: access rules, attribution requirements, and optional settlement conditions.

2
🔐

Gateway 402

Enforce decisions at the edge or origin with allow/deny/rate-limit and optional HTTP 402 challenges.

3
✓

Verify

Verify signed receipts offline (library) or via API for billing, disputes, audits, and partner attestations.

4
📊

Trace

Observe decisions and outcomes as evidence events, then export for audits and operations.

See implementation docsTry a live demo request
PEAC protocol scope
Access
Attribution
Commerce
Consent
Compliance
Privacy
Provenance
Safety
Identity
Purpose
FEATURES

Policy, optional settlement, and proof in one platform

Declare terms, enforce decisions, and verify interaction outcomes with signed receipts.

Traffic visualization
Live
Policy violations blocked

Evidence-first operations

Understand outcomes as evidence events derived from PEAC receipts, not opaque tracking. Filter by issuer, policy hash, endpoint, and decision, then export for audits, disputes, and incident review.

Explore Trace
peac.txt
# AI Agent Policy
User-agent: GPT-*
Allow: /api/public
Disallow: /api/admin
Price: $0.001/request

User-agent: Claude-*
Allow: /
Rate-limit: 100/min

Policy as code

Define interaction terms once. Optionally export compatible views (AIPREF, peac.txt, robots directives) without changing enforcement semantics.

Try Declare
Edge-ready deployment

Edge deployment

Deploy enforcement and verification close to ingress using edge runtimes or self-hosted infrastructure.

View options
402
200

HTTP 402 settlement

HTTP 402 settlement for machine-payable APIs with x402 today and additional rails via adapters (including i402 as planned).

Learn more
Ed25519

Cryptographic receipts

Ed25519-signed receipts for interaction outcomes, verifiable offline with issuer public keys.

View docs
Audit trails

Evidence-Ready

Built-in audit trails and policy hooks so you can verify what happened.

Trust center

From policy to proof

The PEAC standard defines a lifecycle: declare terms, enforce access decisions, optionally request settlement, issue signed receipts, and verify outcomes. Originary provides modular components for each step.

Policy

Declare terms via peac.txt

Access

Enforce with HTTP 402

Settlement (optional)

Adapter-based settlement evidence

Receipt

Signed PEAC-Receipt headers

Trace

Verification endpoints

Portable by design

PEAC receipts work across any conformant implementation. Your policies and decision records are not locked to Originary's platform - they're portable across ecosystems, payment rails, and verification endpoints.

  • Receipts: signed JWS (Ed25519), verifiable offline with issuer public keys
  • Policies: published at /.well-known/peac.txt. No proprietary APIs.
  • Settlement: optional, adapter-based. x402 live, Stripe in preview, custom adapters supported.
  • Verification: pure cryptography. No phone home to Originary servers.

Production components around the standard

Use as much or as little as you need. Each module is independently deployable.

Declare

Generate and publish peac.txt policies with AIPREF snapshots. CLI tool and web UI for policy authoring.

Try Declare

Gateway

HTTP 402 enforcement at the edge. Deploy as middleware or standalone gateway. Works with Cloudflare Workers, Vercel Edge, self-hosted.

View Gateway docs

Verify

Verify PEAC-Receipt signatures offline via JWKS or online via API. Verify any receipt from any PEAC-conformant issuer.

Try verification

Trace

Operational exports for audits and dispute resolution. Export receipts, payment proofs, and policy snapshots as JSONL.

See Trace demo

Adapters

Connect to payment rails (x402, Stripe), AI preference formats (AIPREF), and verification protocols. Extend with custom adapters.

Browse adapters

Deploy it your way

Choose the deployment model that fits your infrastructure, compliance requirements, and operational needs.

Self-hosted

Deploy components in your own infrastructure. Full control, zero vendor dependency.

Edge functions

Run Gateway 402 on Cloudflare Workers, Vercel Edge, or AWS Lambda@Edge.

Managed

Originary-hosted components for teams that want operational support. Contact us for managed deployments.

Integrate in three steps

1

Publish your peac.txt policy at /.well-known/peac.txt

2

Deploy Gateway 402 to enforce access decisions and issue receipts

3

Use Verify to validate receipts from any PEAC-conformant source

Built for ecosystems, not silos

PEAC is designed for organizations that operate in multi-party ecosystems: API providers serving AI builders, content platforms managing inference and training terms, payment networks coordinating settlements, and compliance teams needing auditable decision records. If you need portable, verifiable proof of access decisions, PEAC is for you.

Ship the standard in production

Start with the demo, explore the docs, or talk to us about your use case.

View demoRead the specContact us

Open protocol. No lock-in. Multiple implementations welcome.

Built for teams that need proof

Who is Originary for?

Teams that need receipts, control, and payments for AI and agent traffic.

Legal & Compliance

Audit-grade evidence of consent, attribution, and access terms for AI traffic.

Publishers

Meter and monetize AI access to content with verifiable receipts.

API Builders

Turn agent API calls into billable, compliant transactions.

A2A Networks

Attach receipts to every agent message across rails.

Ready to make AI access verifiable?

Start with Declare to publish policy, then layer on Trace, Gateway 402, and Verify as your AI traffic grows.