llms.txt
Compare with other sites' llms.txt files →# Originary
> Portable signed records for agent actions, API calls, MCP tool runs, gateway
> decisions, payments, approvals, and provisioning, verifiable offline by another
> organization without access to the source system's private logs.
Originary creates portable signed records for agent actions, API calls, MCP
tool runs, gateway decisions, payments, approvals, and provisioning. A record
is issued by a system that observed or reported the action and can be verified
offline with the supplied public key.
When an agent or API action is reviewed or disputed, those records can be
assembled into a bounded evidence case, so another organization can verify what
each issuer reported and identify what evidence is missing, without access to
private logs or an Originary-hosted verifier.
Current protocol release: PEAC v0.16.4 "Local Record Verification Handoff",
which adds browser-based local verification of a signed record against a
supplied public key with no network access, RFC 7493 I-JSON enforcement on
record issuance, and a cross-organization verification handoff guide. The
wire format is unchanged. Earlier evidence patterns remain available: paid
resources, paid MCP tool records, linked counterparty acknowledgments, Merkle
commitment helpers, external evidence anchoring, agent spend attribution,
agent run lineage records, action approval records, and runtime lineage
exports.
Last updated: 2026-10-24
Organization: Originary (legal entity: Poem, Inc.)
Location: Delaware, USA
Contact: contact@originary.xyz
## What it is
Verifiable records for agents, APIs, and gateways. Each record is issued by a
system that observed or reported the action, and verifies offline against the
issuer's public key. For reviewed or disputed actions, Originary connects
selected signed records and native artifacts into an evidence case, so another
organization can verify what each issuer reported and identify what evidence is
still missing, without internal logs, dashboard access, or vendor runtime.
## Why we build this
As agents take on real work, the only record of what they did sits inside the
systems that run them, so the people an action affects have to ask for it and
accept what they are shown. A signed record travels with the action instead:
anyone it affects can check, with the issuer's public key, what was recorded and
who stands behind it, without access to the operator's systems. Originary builds
an open protocol (PEAC Protocol), the tools to issue, verify and package signed
records, and Verification Pilots that put them into one production workflow at
a time.
## Core pages
- [Home](https://www.originary.xyz/)
- [Product](https://www.originary.xyz/product)
- [Evidence case](https://www.originary.xyz/evidence-case): what a bounded evidence case contains, with a downloadable illustrative example
- [Action review](https://www.originary.xyz/action-review): review agent-driven operations where source reports disagree; six exception rules, case disposition and an interactive synthetic demo
- [Investigate](https://www.originary.xyz/investigate): turn a disputed agent action into a reviewable evidence case, with cited findings, missing evidence and a recipient decision
- [Audit and incident handoff](https://www.originary.xyz/audit-incident-handoff): assembling and verifying an evidence handoff bundle
- [AI compliance evidence](https://www.originary.xyz/ai-compliance): AI compliance evidence: how Originary creates and verifies portable signed records for selected agent actions, API calls, gateway decisions, approvals, payments and provisioning changes.
- [About](https://www.originary.xyz/about): mission, the thesis (whoever holds the logs holds the story), and what Originary builds: an open protocol, the tools, and Verification Pilots
- [PEAC Protocol](https://www.originary.xyz/peac)
- [Downloads](https://www.originary.xyz/downloads): Originary Downloads: PEAC Protocol source code, CLI, SDK packages, and verification tooling from the official repository and package registries
- [Plans and pilot](https://www.originary.xyz/pricing)
- [Contact](https://www.originary.xyz/contact)
- [Trust](https://www.originary.xyz/trust): deployment and verification boundaries, procurement facts, and per-system interoperability status
- [Press](https://www.originary.xyz/press): press kit: quotable boilerplate, fast facts, current metrics, and logo downloads
- [Security](https://www.originary.xyz/security): supported versions, severity and response targets, and supply-chain posture
## Product pages
- [How it works](https://www.originary.xyz/how-it-works): the four-stage model (observe, issue, verify, hand off), with the six record surfaces in detail
- [Records](https://www.originary.xyz/records): gallery of signed record types (MCP, API, gateway, agent, payment, provisioning), each verifiable offline
- [Verify](https://www.originary.xyz/verify): verify a signed record with the issuer's public key; offline by design, nothing stored
- [MCP](https://www.originary.xyz/mcp): keep a verifiable record of important MCP tool calls
- [AI gateway](https://www.originary.xyz/ai-gateway): independently verifiable AI gateway decisions
- [Provisioning records](https://www.originary.xyz/provisioning-records): signed records for deployments, provider setup, credentials, budgets, and resource lifecycle events
- [Agentic commerce](https://www.originary.xyz/agentic-commerce): evidence for paid APIs, MCP tools, and agent commerce
## Blog
- [Blog](https://www.originary.xyz/blog)
## Current articles
- [AI agent audit trail handoff](https://www.originary.xyz/blog/ai-agent-audit-trail-handoff)
- [MCP tool call audit evidence](https://www.originary.xyz/blog/mcp-tool-call-audit-evidence)
- [AI gateway audit logs policy decisions](https://www.originary.xyz/blog/ai-gateway-audit-logs-policy-decisions)
- [Agentic commerce payment fulfillment evidence](https://www.originary.xyz/blog/agentic-commerce-payment-fulfillment-evidence)
- [AI agent customer requests completion](https://www.originary.xyz/blog/ai-agent-customer-requests-completion)
- [Verifiable provisioning records agent infrastructure](https://www.originary.xyz/blog/verifiable-provisioning-records-agent-infrastructure)
- [What is http 402](https://www.originary.xyz/blog/what-is-http-402)
- [A2a stack agent to agent commerce](https://www.originary.xyz/blog/a2a-stack-agent-to-agent-commerce)
- [Aipref by ietf](https://www.originary.xyz/blog/aipref-by-ietf)
- [Robots txt rfc 9309](https://www.originary.xyz/blog/robots-txt-rfc-9309)
## Brand assets
The Originary wordmark (brand guidelines v17), for correct attribution. Reproduce
it only from these files: ink on white or light greys, the reverse file on ink or
dark greys, never recoloured, retyped or re-spaced. Below 96 px wide, use the app
icon. No partnership, certification, or endorsement is implied by use of these files.
- [Brand kit](https://www.originary.xyz/brand/originary-brand-kit-v17-2026-10-12-cobalt.zip): every file below plus favicons and design tokens, ZIP
- [Originary wordmark](https://www.originary.xyz/brand/wordmark/originary-wordmark.svg): ink master, SVG
- [Originary wordmark reverse](https://www.originary.xyz/brand/wordmark/originary-wordmark-reverse.svg): for dark backgrounds, SVG
- [Originary wordmark 800w](https://www.originary.xyz/brand/wordmark/originary-wordmark-800w.png): raster, 800 px wide
- [Originary wordmark 2400w](https://www.originary.xyz/brand/wordmark/originary-wordmark-2400w.png): raster, 2400 px wide
- [Originary wordmark reverse 800w](https://www.originary.xyz/brand/wordmark/originary-wordmark-reverse-800w.png): for dark backgrounds, raster
- [Originary app icon](https://www.originary.xyz/brand/app-icon/originary-app-icon.svg): app icon and avatar tile, SVG
- [Originary link preview](https://www.originary.xyz/brand/social/originary-link-preview-1200x630.png): 1200 x 630
## Open protocol
PEAC Protocol is an Apache-2.0 open-source project for portable signed
interaction records, maintained by Originary.
- [peacprotocol/peac](https://github.com/peacprotocol/peac)
## Notes
Originary does not replace gateways, observability, payment rails, policy
engines, or runtimes. It records selected facts so another party can later
verify what the issuer recorded.
Site analytics on originary.xyz load only after a visitor opts in, and never
under Global Privacy Control or Do Not Track. The Verify page checks records in
the browser; nothing pasted there is uploaded or session-recorded.