“The model is not the bottleneck anymore.
Trusting what it just did is.”
The receipt your auditor will ask for in 18 months is the same receipt we cut on day one.
You already log this. A log is not a receipt.
Your database keeps a record for you. A receipt is what you hand to someone who does not trust you. Five reasons the first cannot do the second.
We are not a replacement for your database. We are the layer that turns the line in your database into a receipt the outside world can verify without asking your permission.
Five steps from your AI to a public receipt. No new tools to learn.
- 1Step 1Listen
When your AI agent acts, we listen.
Wrap an Anthropic or OpenAI client, or create a DR-1 record at the decision boundary with the builder.
SDK wrappers · DR-1 builder - 2Step 2Format
We give the decision a passport.
A standard, language-neutral record auditors recognize — what the AI saw, what it considered, what it picked, and why.
DR-1 schema · 12 fields - 3Step 3Bundle
Many decisions, one tamper-proof stamp.
Hundreds of records get folded into a single fingerprint. Change one byte anywhere — the fingerprint breaks.
Merkle batch - 4Step 4Anchor
Sealed with public-blockchain ink.
The bundle stamp is written to a public, neutral chain. Once it lands, no one can erase it — not even us.
Base L2 · EAS - 5Step 5Prove
Anyone can verify it. Forever.
Customers, regulators, auditors, your insurer — all hit the same public URL. Six independent checks must pass.
Public verifier · printable receipt
Pick a scenario. Watch the decision verify itself.
What we are. What we are not.
Plaid for AI agents. Carfax for AI decisions. We sit between operators and verifiers — and never on either side.
A neutral notary.
An independent attester anchors every Merkle root on a public chain. Operators can't rewrite their own logs.
An integrator.
LLM client wrappers, Merkle trees, on-chain attestations. Battle-tested public goods, assembled into a new primitive.
An open protocol.
DR-1 is MIT-licensed and proposed for ISO/IEC 24970. The standard is the moat — not the implementation.
Not insurance.
We don't underwrite risk. We don't pay claims. AI insurers are our customers, not our competitors.
Not custody.
We never hold customer funds. Ever. The platform attester wallet pays gas — that's the only money we touch.
Not a verdict.
We don't decide who's at fault. We make the facts cryptographically certain. Judges decide what they mean.
Plain numbers. Both sides of the receipt.
Operators pay to anchor. Verifiers pay to check. Neither side subsidizes the other — that is what keeps us neutral.
For developers wiring trace.ai into a prototype. Real attestations, on testnet.
- 1,000 anchored decisions / mo
- 1 AI agent
- Base Sepolia (testnet)
- Public verifier URL
- DR-1 schema validation
- Community support
For teams shipping AI agents to customers. Mainnet, branding, support.
- 100,000 anchored decisions / mo
- Up to 10 agents
- Base mainnet anchoring
- Branded verifier domain
- Print-ready receipts (PDF + QR)
- 99.9% uptime SLA
- Priority email support
For regulated industries: finance, health, legal. Built for auditors who arrive unannounced.
- Unlimited decisions
- Unlimited agents
- Dedicated notary wallet
- VPC / on-prem option
- Custom DR-1 extensions
- SOC 2 · ISO 27001 · GDPR
- Insurance partner integration
- 24/7 incident response
Either side can walk away. That is the point — a receipt nobody is forced to keep is a receipt no one is forced to trust.
Adjacent, not overlapping. Three categories. One open quadrant.
The market has tooling for the AI team, dashboards for the compliance team, and insurance for the CFO. Nobody is shipping receipts the outsider can verify without permission.
The other three are real, growing, and necessary. They are also, taken together, what trace.ai customers buy alongside us. Receipts are the substrate the rest sits on.
From a single vertical, to the receipt of record.
Three phases. Each one builds the receipts the next phase rests on. No grand pivots; the schema we ship today is the schema regulators will reference in 2028.
MGA
Win one vertical decisively.
- Bloom Co. live with anchored receipts on Base
- KAIA & EU AI Act compliance kit shipped
- 3 paid design partners across e-commerce, finance, healthcare
- DR-1 schema v1.0 frozen, MIT-licensed
Platform
Open the receipts market to anyone.
- Multi-tenant SDK · public verifier API
- Third-party auditor & insurer integrations
- $0.001/verification metered marketplace
- Multi-chain anchor support (Base + L1)
Standard
DR-1 becomes the receipt regulators ask for.
- DR-1 referenced in jurisdictional guidance
- ISO/IEC working-group alignment
- 1B+ anchored receipts across operators
- Receipts-as-collateral for AI insurance
Phase 1 is what we sell today. Phase 2 is what we expand into with the receipts already anchored. Phase 3 is what regulators converge on once the schema is in production at scale.
One line. That's the integration.
Drop into any AI agent. We piggyback on the standard instrumentation tools you may already use; no new vocabulary to learn.
// pnpm add @vibingminers/sdk @anthropic-ai/sdk
import Anthropic from '@anthropic-ai/sdk';
import { traceClaude } from '@vibingminers/sdk';
// One wrap. Every messages.create now ships a receipt.
const claude = traceClaude(new Anthropic(), {
agentId: 'cs-agent-v3',
});
const response = await claude.messages.create({
model: 'claude-opus-4-7',
messages: [{ role: 'user', content: prompt }],
trace: { decisionClass: 'approve',
rationale: 'within refund window' },
});
// → standard Anthropic response
// → receipt anchored on Base Sepolia in < 60s
// → verifier URL logged: /verify?id=<decision_id>