A verifiable interaction record is portable proof of what an agent did
Each record is a signed artifact containing what happened, what policy applied, and what decision was made. Verify it offline with the public key alone.
What records provide
Signed records for every interaction, verifiable against published public keys.
Signature-Verified
JWS payloads with Ed25519 signatures. Tamper-evident by design.
Policy Binding
Carries a policy digest. Verifiers confirm binding when the policy snapshot is available (evidence bundle or local cache).
Offline Verification
Verify against published JWKS endpoints. No API call required.
Timestamped
Precise iat/exp claims establish when interactions occurred.
Payment Evidence
Transaction references and payment rail details included.
Audit Ready
Export verifiable records for audit, compliance, and dispute resolution.
Privacy Modes
Strict, balanced, or custom identifier handling for compliance.
Attestations
Extensible evidence types for risk, consent, and compliance.
Record anatomy
Each signed record is a JWS payload containing interaction metadata, policy bindings, and optional payment evidence.
{
"header": {
"alg": "EdDSA",
"typ": "interaction-record+jwt",
"kid": "originary-2026-01"
},
"payload": {
"iss": "https://www.originary.xyz",
"iat": 1734048000,
"jti": "rcpt_7f92ab31",
"peac": {
"version": "0.12.3",
"resource": "/api/content",
"policy_hash": "sha256:9f3c..."
},
"payment": {
"rail": "x402",
"amount": "0.10"
}
},
"signature": "base64url..."
}Built for real workflows
From internal audits to dispute resolution, records provide the evidence trail you need.
Internal Audits
Detailed records of AI interactions for governance and risk management.
Content Licensing
Verify content was accessed according to licensing terms.
Dispute Resolution
Verifiable evidence when disputes arise about terms.
Usage Analytics
Track AI access patterns with verifiable records.
Payment Reconciliation
Match payments to specific API interactions.
Policy Compliance
Demonstrate interactions occurred under specific policies.
Verification in 3 steps
Verify any record against published keys, no API required.
Extract header
Parse the JWS header to get the key ID (kid)
Fetch public key
Retrieve the key from /.well-known/jwks.json
Verify signature
Validate Ed25519 signature against payload
Signed records provide evidence of interactions and policy snapshots. How this evidence is interpreted in legal or regulatory contexts depends on jurisdiction and specific circumstances. Consult legal counsel for compliance guidance.
Ready to add signed records?
Start generating verifiable records for every AI interaction with Originary.