Public audit layer · v1.0.0
The receipt for the
data that trains the
future.
Every photo, voice sample, expert annotation becomes an immutable receipt. Trace is where labs verify provenance, contributors confirm consent, and regulators audit the source.
Receipts on the Protocol
35,300,058
indexed · live
Contributors
33,906,086
Data audited
9.70 TB
Look up a receipt
Enter a hash or data ID to see its full record
Receipts as they happen.
Registrations and metadata updates. Every event on the Protocol surfaces here, anonymized, sectioned by category.
Example · dataset audit
What we calculate for
a dataset.
Hand Trace the record list behind a dataset you're evaluating, and it computes the compliance posture over that exact set. Here's a sample audit of 12,480 records, and every number in a real one links back to the receipts that produced it.
KYC verified
96.4%
of contributors in the set
On latest TOS
91.8%
consent version coverage
Total size
1.42 TB
avg 119 MB per file
Media coverage of the set
Sample dataSample figures. A real audit also breaks the set down by TOS / PP version, KYC status, file type, and contributing app, with a per-record drill-down and CSV export.
Contributing apps
Each app brings its own consent posture, KYC provider, and operating model. Click in to verify any of them.
Kled
Sourcing the largest licensable datasets on the planet
Receipts
31,750,004
Numo
Audio & video data collection
Receipts
333,755
oto
Voice & conversational audio
Receipts
3,216,299
Coming soonMiso
Long-tail multimodal & sensor data
Receipts
—
For frontier labs
Before you license a single byte, verify the whole set.
Drop in a CSV of hashes, or a pre-generated URL from the contributing app, and Trace renders the aggregate posture: consent coverage, TOS versions, KYC verification, media-type spread, file-size totals. Drill into any individual record.
A data contributor? Verify your own file →
What labs see
% under each TOS version
with content-addressed pointers
% from KYC-verified contributors
by provider and posture
Media · MIME coverage
video · image · document, by mime_type
File-size posture
totals, averages, byte-level deltas
Metadata-update history
seq 1–20, prev/next root chain
How a receipt arrives
From upload to onchain in seconds.
Webhook in, indexed and verifiable in well under a minute. The onchain registry is the source of truth; everything else is an index of it.
App ingests
Contributing app collects a piece of data with explicit consent. Sensitive metadata stays in the app's own system.
1
Webhook to Trace
App posts a SHA-256-anchored receipt over an HMAC-signed webhook. One asset per call, idempotent by event key.
2
Onchain register
Trace batches receipts into a Merkle root and registers via the Data Foundation. Lifecycle events append over time.
3
Public lookup
Indexed, searchable, downloadable. Labs verify datasets. Contributors confirm consent. Regulators audit.
4