Audit-grade receipts for AI voice agents.Signed at the moment of the call. Verified by any third party. Designed for TCPA defense.

When an AI bot calls a consumer on behalf of a brand, Adjuro issues a signed receipt that proves who the agent is, what consent authorized the call, on whose behalf, at what timestamp—verifiable by any third party in under 50 milliseconds.

Public transparency log + did:web + JWKS — federated trust infrastructure for AI agent attestation.

90-Second Demo

Vapi outbound call → Adjuro receipt → verify roundtrip. Recording lands this week — book a call to see it live.

90 SEC · VAPI OUTBOUND CALL → ADJURO RECEIPT → VERIFY ROUNDTRIP

Get a Demo → Verify a Receipt → Read the Receipt Schema →

Compliance buyers and TCPA defense counsel: book a 30-minute call. Open-source verifier SDK launching Saturday 2026-05-23.

I.THE PROBLEM TCPA class-action exposure is the compliance bomb of 2025–2026.

$6.6M

Average TCPA class-action settlement in 2024–2025 (Womble Bond Dickinson). The Lowery v. OpenAI / Twilio lawsuit (ongoing 2026) now exposes platforms to $500–$1,500 per call for downstream consent failures. Henson Legal: "the compliance bomb of 2025 with reverberations throughout 2026."

Federal TCPA cases, 2025

2,628

CompliancePoint · 60% YoY

Class-action share

~80%

ActiveProspect

Q1 2025 class actions

507

+112% over Q1 2024

Per-call exposure

$500–1,500

Lowery v. OpenAI / Twilio

What compliance teams resort to today

Compliance teams reconstruct consent post-hoc from CRM exports, IVR recordings, and email archives — 10–40 hours per discovery request, evidence that opposing counsel routinely challenges as non-contemporaneous.

Fraud teams either accept all AI agent traffic and absorb fraud risk, or block all AI agent traffic and break legitimate workflows. There is no middle option.

Analytics teams cannot attribute call outcomes to specific agents, campaigns, or consent sources without manual joining across systems.

Aggregate cost per mid-market contact center: estimated $50K–$200K/year in compliance ops, fraud loss, and manual audit prep.

II.THE RECEIPT A signed JWS payload. Court-admissible by design. Verifiable in <50ms.

Every Adjuro receipt is a JOSE-standard JWS signed with Ed25519 (RFC 8032) via AWS KMS. Both standard claims (iss, jti, iat, exp) and human-readable aliases ship in the same payload.

{ "iss": "https://api.adjuro.ai", "jti": "adj_rcpt_x9k2tqp4f7a3w1n5b8c2d6e3", "iat": 1779286854, "exp": 1810822854, "agent_id": "adj:7k9n2p4f8m1q5w3r6t2y8u4i", "tenant_id": "acme-collections-mid-atlantic", "brand": "Acme Collections", "trust_root_id": "adjuro-root-sample", "event_type": "voice_call", "caller_number": "+18005551212", "callee_hash": "sha256-hmac:a8j1bzs9c5y2v7m6p4n3f8d2", "campaign_id": "acct-recovery-q2-2026", "consent_id": "crm-12847-consent-2026-03-14", "scope": ["debt_collection"], "jurisdiction": "US-CA", "issued_at": "2026-05-20T14:20:54.366Z", "expires_at": "2027-05-20T14:20:54.366Z" }

agent_id — deterministic hash of tenant + agent name. Proves which agent placed the call.

consent_id — opaque reference to the consent artifact in the tenant's CRM. Adjuro stores; never resolves.

scope — V0 enum: account_servicing, appointment_reminder, debt_collection, marketing, support, verification.

jurisdiction — ISO 3166-2. Determines which consent regime applies (TCPA, GDPR, HIPAA, state telemedicine).

trust_root_id — federation-aware. adjuro-root-* in V0; reserved for Vapi / Retell roots.

callee_hash — HMAC-SHA256 of recipient E.164 under per-tenant salt. Verifier proves the hash was signed; never reverses it.

III.HOW IT WORKS Three calls. Sign at issue. Verify offline. Export the audit packet.

A · ISSUEBefore each outbound call, your application asks Adjuro to sign a receipt binding the agent, the consent reference, and the call metadata.

# POST /v1/consent-receipts
curl -X POST https://api.adjuro.ai/v1/consent-receipts \
  -H "Authorization: Bearer $ADJURO_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_id": "adj:7k9n2p4f8m1q5w3r6t2y8u4i",
    "brand": "Acme Collections",
    "caller_number": "+18005551212",
    "callee_hash": "sha256-hmac:a8j1bzs9c5y2v7m6p4n3f8d2k1",
    "campaign_id": "acct-recovery-q2-2026",
    "consent_id": "crm-12847",
    "scope": ["debt_collection"],
    "jurisdiction": "US-CA",
    "timestamp": "2026-05-19T14:32:23Z",
    "nonce": "a1b2c3d4e5f60718",
    "event_type": "voice_call"
  }'

# → 201 { "receipt_id": "adj_rcpt_x9k2tqp4...", "receipt_jws": "eyJh...",
#         "verify_token": "...", "status": "pending" }

B · VERIFYAny third party — a contact center, a law firm, opposing counsel — verifies the signature against the published JWKS. Offline after the JWKS is cached; no Adjuro account required.

// npm install adjuro
import { verifyReceipt } from "adjuro";

const result = await verifyReceipt(receiptJws);

// → { valid: true, kid: "adjuro-root-2026w20",
//      receipt_id: "adj_rcpt_x9k2tqp4...",
//      issued_at: "2026-05-19T14:32:23Z",
//      payload: { agent_id: "adj:7k9n...", scope: ["debt_collection"], ... } }

C · EXPORTFor discovery, audit, or a motion to dismiss: the receipt, the JWKS at time of issuance, and packet metadata, bundled into a signed ZIP.

# GET /v1/calls/:receipt_id/evidence
curl https://api.adjuro.ai/v1/calls/adj_rcpt_x9k2tqp4.../evidence \
  -H "Authorization: Bearer $ADJURO_KEY" \
  -o evidence.zip

unzip -l evidence.zip
# metadata.json
# receipts/adj_rcpt_x9k2tqp4....jws
# jwks-at-time-of-issuance.json
# README.txt

Verify a receipt now — runs in your browser, no account needed.

Sample receipt (editable) — signed at build time with a real Ed25519 key

IV.WHY ADJURO Court-admissible. Federated. Open source.

Court-Admissible by Design

The receipt does not need to prove the recipient is who the receipt claims; it needs to prove the tenant attested at call time. That is enough for TCPA defense: the tenant produces the signed receipt and says "we attested consent was captured at this timestamp; here is the cryptographic proof of that attestation." Pure Ed25519 (RFC 8032) signed inside AWS KMS HSM. Every audit packet ships with the receipt and the JWKS at time of issuance — designed to pass Federal Rule of Evidence 901 without an expert witness explaining a hash.

Federated Trust Network

The Linux Foundation Agentic AI Foundation, NIST AI Agent Standards Initiative, IETF AIMS draft, and ERC-8004 mainnet deployment are all evidence the category exists. Standards bodies aren't competitors; they're validation. Three trust roots ship in V0: adjuro-root-2026w20 active, vapi-root-reserved and retell-root-reserved as placeholders. When a voice-agent platform runs its own signing root, every receipt it issues verifies through the same registry without retrofit. We run the verifier registry, not the only issuer — cross-trust-boundary neutrality is the structural defense incumbents can't replicate.

Open Source from Day One

Compliance teams buy before fraud teams do. TCPA litigation budget is structurally bigger than fraud-prevention budget because settlements concentrate ($6.6M mean) while fraud spreads thin. Compliance buyers demand artifacts they can hand to defense counsel without licensing terms. The verifier SDK ships Saturday 2026-05-23 as adjuro on npm (Apache 2.0, ~400 lines), with the public transparency log launching alongside it — append-only Merkle tree, daily signed snapshots at 09:00 UTC. Every receipt verifiable by anyone, forever, with no Adjuro account required.

V · BOOK A CALL

Talk to the people building it.

30 minutes. Real questions. No deck. Compliance and legal get a verifier walkthrough; engineering gets a federation deep-dive.

Verify a receipt right now — no form needed.

30 minutes with the team building it. No SDR, no qualification call.

Open-source verifier ships Saturday 2026-05-23. Evaluate before you talk to us.

Federation-aware. If you run a voice-agent platform, we'll wire your signing root.

OPEN SOURCE · APACHE 2.0 VERIFIER ON NPM · 2026-05-23 FEDERATED TRUST ROOTS

Book a 30-minute call

We'll route to the right person based on your role.

Leave this field empty

Work email

Company

Role

What's driving this?

Monthly AI call volume

No spam. We'll reply within one business day.

THE TRUST INFRASTRUCTURE, BY THE NUMBERS

Day-1 verifications
complete

6 / 6

VAPI + KMS · 2026-05-17

V0 endpoints
live

AGENTS · RECEIPTS · VERIFY · EVIDENCE · WEBHOOKS · JWKS · LOG · REVOCATIONS · API-RECEIPTS

Test suite
passing

145

BUN TEST · MAIN · 24 FILES

Transparency log

2026-05-23

LOG.ADJURO.AI · LAUNCHING SAT

OSS verifier SDK

2026-05-23

NPM · adjuro · APACHE 2.0

Ed25519 KMS
verified

2026-05-17

AWS KMS · US-EAST-1 · ECC_NIST_EDWARDS25519