INTERACTIVE DEMO

How Originary works

Originary provides enterprise infrastructure for the open PEAC protocol. Watch agents discover your policies via peac.txt and aipref.json, complete transactions through Originary Gateway (402), and generate verifiable receipts.

PEAC protocol flow via Originary

From policy discovery to cryptographic proof. Click any step to explore.

Agent request

Policy discovery

Terms evaluation

Decision engine

Payment gateway

Resource access

PEAC receipt

Receipt verification

Agent request

Autonomous agent needs your API or content

PEAC-Receipt header and verification

Cryptographically signed proof of transaction with instant verification

Response with PEAC-Receipt

HTTP/1.1 200 OK
Content-Type: application/json
PEAC-Receipt: eyJhbGciOiJFZERTQSIsImt...
...pQ2nY6jL8vW4tZ1cH5sA0bN9oE4qI6dF3gU2wP7hT8xM

{"status": "success", "data": {...}}

Originary Verify API result

POST https://api.originary.xyz/verify
Content-Type: application/json

{"receipt": "eyJhbGciOiJFZERTQSI..."}

→ Response:

{
  "valid": true,
  "receipt_id": "urn:originary:...",
  "issued_at": "2025-10-06T08:15:00Z",
  "issuer": {
    "name": "Originary",
    "domain": "originary.xyz",
    "verified": true
  },
  "settlement": {
    "gateway": "Originary Gateway (402)",
    "payment_id": "pay_orig_2025_xyz123",
    "amount": {"value": 0.05, "currency": "USD"},
    "status": "confirmed"
  },
  "signature_verified": true,
  "timestamp_valid": true
}

✓ Cryptographic proof: Each PEAC-Receipt is signed with EdDSA (Ed25519) and can be independently verified via Originary Verify API or the open PEAC protocol specification.

PEAC policy file

Your /.well-known/peac.txt served by Originary

preferencesAIPREF URL

access_controlhttp-402

payments[x402]

provenancec2pa

receiptsrequired, verify

public_keys[ {kid, alg, key} ]

peac.txtaipref.jsonsecurity.txtrobots.txtads.txtapp-ads.txthumans.txtassetlinks.jsonllms.txt

Live transaction flow

Watch Originary orchestrate a complete agent transaction

1. Policy discoverydiscover

Agent fetches peac.txt via Originary

2. Terms checkprefs

Originary evaluates peac.txt and aipref.json

3. Policy engineevaluate

Originary decides: allow, deny, or payment

4. Payment flowsettle

Originary Gateway (402) processes payment

5. Generate proofreceipt

Signed PEAC receipt (JWS)

6. Verify receiptverify

Originary Verify API confirms authenticity

PEAC Receipt (JWS)

// Cryptographically signed PEAC receipts
// Receipt will appear during the proof generation step

Step 1 / 6 - Pace ~1600ms