The data

Pull a signed slice
of the record.

Everything the warehouse distills leaves through one metered door: the Data Extract API. Streams declare their grain, slices page on honest keyset cursors, and every response carries a signature you can verify offline against published keys.

Join Alpha Verify a receipt

01The warehouse

Four planes in. One door out.

Four ingest planes land in one lakehouse as day-rows, and everything leaves through one metered, signed door: the Data Extract API. As of July 2026 the door serves 24 signed streams and 4 keyed lookups spanning news digests, the frozen daily archive, feed facts with supersession chains, claim witnesses, open signals, chain instrument readings, and infrastructure telemetry.

News

The world news scan: articles, signed digests, the frozen daily archive, and the fact layer distilled from them.

Open signals

Prediction markets, legislation, macro releases, and seismic events, each row signed on its own path.

Internet telemetry

DNS and infrastructure movement: domains scanned, fingerprints, and change detection over time.

Chain scanners

Daily chain readings from our own instruments: Morpheus via MorScan, Bittensor via dTAOscan, signed at the reading.

4 ingest planes -> lakehouse day-rows -> one metered, signed door.

02The contract

Every slice carries its receipt with it.

A pull returns rows, an opaque cursor for the next slice, and a receipt: the slice's content hash, signed Ed25519 with a published key. Verification runs offline, in your code, against the DRM3 signer registry at status.drm3.network. The signature proves who served the slice and that it arrived unaltered; it is added trust on top of the data, never a claim that a statement inside it is true.

Keyset cursors

Honest paging that never skips or repeats a row, resumable from the cursor you hold.

Slice receipts

Content hash + Ed25519 signature on every response. Keys published, rotations on the record.

Self-describing

Every stream states its grain, its keyset, its fields, and exactly what the signature covers.

03Pull it

One pull to your first verified slice.

# pull a slice; the response carries rows + next cursor + signed receipt
curl -H "X-DRM3-Data-Key: $KEY" "$DRM3_DATA_API/v1/streams/world-news/pull?limit=100"

# verify the slice signature against the published DRM3 signer registry
curl "https://status.drm3.network/.well-known/drm3-keys.json"

Materialize-first is the intended shape: pull the slice into your own store and serve your product from there, resuming from the cursor you hold. Access is always a scoped key you can rotate, never a service account.

If a slice ever fails verification, you hold the proof that it did. That is the entire point.

04Metered

Priced per row, scoped per key.

Pulls meter per row against the key that made them, and entitlements are tenant-scoped capability tokens that gate streams individually, so a key sees exactly what its tenant bought and nothing else. Our own apps buy access through this same door; nothing first-party gets a backstage key.

drm3:world-newsdrm3:morpheusdrm3:bittensordrm3:dnsdrm3:knowledge

Honest status: the door and per-row metering are live. Wallet debit (phase 2) is in progress, so per-request wallet debit is not live yet.

DOOR + METERING: LIVEWALLET DEBIT: PHASE 2 IN PROGRESS

Want a key? Create an account or contact support.

The record is the product. This is the tap.

Join Alpha How the record works

Questions about streams or entitlements: contact support.