Originary blog
Portable records for agents, APIs, and automated work
The Originary blog covers agent verification, signed records, policy, offline verification, evidence workflows, and the open infrastructure needed for automated interactions. Technical articles, protocol updates, and best practices from the Originary team.
All Articles
Agent and Crawler Signals: Turning Unknown AI Traffic Into Verifiable Records
Agent and crawler identification is more than classifiers. Learn how metadata, fingerprints, and signed records turn AI traffic into verifiable records for audits and disputes.
The A2A Stack: Agent-to-Agent Verification and Commerce
How AI agents coordinate, transact, and verify interactions with each other. The A2A stack covers policy discovery, signed records, and cross-boundary proof.
What is HTTP 402? How PEAC Uses 402 for Agent Payments
HTTP 402 Payment Required was defined in 1997 and reserved for digital payments. Learn how PEAC Protocol activates 402 for AI access control, agent payments, and verifiable receipts.
From Detection To Settlement: Using PEAC To Turn AI Traffic Into Revenue And Compliance
How Originary and PEAC connect agent and crawler identification signals to HTTP 402, x402, and Stripe, with signed records for billing, audit, and compliance.
AIPREF: A Common Language for AI Usage Preferences
Understanding the IETF AIPREF specification for expressing AI usage preferences through HTTP headers and robots.txt - what it is, how it works, and how to implement it today.
HTTP 402 for APIs: Making Payment-Required Responses Work
A practical guide to implementing HTTP 402 Payment Required in modern APIs. Learn the anatomy of a 402 response, receipt verification patterns, and how to avoid common pitfalls.
Add HTTP 402 to Your API in 15 Minutes
Quick tutorial for adding HTTP 402 Payment Required responses to an existing Express API. No SDK required, just standard HTTP and receipt verification.
HTTP 402 on Cloudflare Workers: Global Edge Payment Gates
Deploy HTTP 402 payment-required responses at the edge with Cloudflare Workers. Zero cold starts, global KV storage, Web Crypto API for receipt verification.
robots.txt (RFC 9309): The Web's Crawl Access Control
A technical deep dive into RFC 9309, the standardized Robots Exclusion Protocol - matching rules, error handling, caching, and how it relates to AIPREF usage preferences.
Stay updated on the agentic web
Get the latest insights on AI preferences, protocol updates, and best practices delivered to your inbox