API PROVIDERS

When agents call your API, keep proof

Publish machine-readable terms with peac.txt. Verify agent requests at the boundary. Return a verifiable interaction record for every decision. Records are portable, offline-verifiable, and built on the PEAC open standard.

What Originary adds to your API

Policy discovery

Agents discover your terms through a standard peac.txt policy file at a well-known endpoint. No proprietary integration required.

Request verification

Evaluate agent requests, apply your access and rate-limit policy, and issue a signed record of the decision. Works with your existing auth and gateway.

HTTP 402 flows

For priced endpoints, return HTTP 402 with a payment hint. Agents pay and retry with a verifiable receipt. Adapters available for x402 flows.

How it works

  1. Publish a peac.txt policy file at /.well-known/peac.txt
  2. Add Originary middleware to evaluate inbound requests
  3. Your rules decide: allow, deny, rate-limit, or challenge with HTTP 402
  4. A signed interaction record is returned in the PEAC-Receipt header
  5. Records are portable: your team can inspect, export, and use them in audits or disputes

Get started

Start with a peac.txt policy and Express middleware. Add HTTP 402 flows when you need priced access.