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 specGet started in 10 minutes
POLICY
/.well-known/peac.txt
📋
Policy
🔑
Access
💳
Payment
✅
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

Works with

How it works

Deploy policy once. Enforce at the edge. Verify every outcome.

1
📋

Declare

Define terms for agents: access rules, payment requirements, and attribution.

2
🔐

Gateway 402

Enforce policy at the edge with allow/deny/rate-limit or HTTP 402 challenges.

3
✓

Verify

Validate signed receipts server-side for billing, disputes, and audits.

4
📊

Trace

Observe agent traffic and outcomes, export logs and proofs to your stack.

See implementation docsTry a live demo request
Seven pillars of PEAC
Access
Attribution
Consent
Commerce
Compliance
Privacy
Provenance
FEATURES

Policy, payments, and proof in one platform

Declare terms, gate access, and verify every AI interaction with signed receipts.

Traffic visualization
Live
Policy violations blocked

Real-time Bot Analytics

See every AI crawler, agent, and bot hitting your endpoints. Filter by type, block bad actors, and analyze traffic patterns.

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 your AI policy once. Export to AIPREF, peac.txt, and robots.txt automatically.

Try Declare
Edge-ready deployment

Edge Deployment

Deploy verification at the edge via Cloudflare Workers or Vercel.

View options
402
200

HTTP 402 Payments

HTTP 402 payments for machine payable APIs with x402 today and i402 on the roadmap.

Learn more
Ed25519

Cryptographic Receipts

Ed25519 signed proofs for every transaction.

View docs
Audit trails

Evidence-Ready

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

Trust center

From policy to proof

The PEAC standard defines a complete lifecycle: declare terms, enforce access decisions, settle payments, issue signed receipts, and verify outcomes. Originary provides production-ready components for every step.

Policy

Declare terms via peac.txt

Access

Enforce with HTTP 402

Settlement

Multi-rail payment support

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 are JWT-signed and verifiable by any party with your public key
  • Policies are published at /.well-known/peac.txt - no proprietary APIs required
  • Multiple payment rails (X402, Stripe, custom) with normalized payment{} objects

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 with SLA guarantees. Contact us for enterprise 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 provable?

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