SDK
One SDK. Every DRM3 integration.
drm3 CLI.One package, subpath imports
Import only what you use. Every capability is its own entry point, so a browser bundle that just verifies receipts never pulls in the payment core.
The umbrella: the network client, everything below re-exported.
Offline SSO: verify a DRM3 identity token in-process, no call home.
The in-browser receipt viewer + verifier: check an Ed25519 receipt live against the public registry.
The x402 payment gateway core: answer a 402 with terms, take the pay-per-call.
Metering: read a user's live credit balance and debit per use.
The Extract door: read lakehouse data through the signed, metered Data Extract API, no service account. Every page is provenance-verified before its rows are handed back.
The Ingest door: write rows into the lakehouse through the signed, metered door, no service account. Dedupes on your insertId and returns a verified batch receipt.
Record search: query the DRM3 fact record and page through signed article results.
The cross-app switcher: move a signed-in user between DRM3 apps.
Cross-app alerts: surface a user's notifications in any window.
Partner key management: generate, rotate, and CSR signing keys.
Compiled JavaScript plus TypeScript types. Installs everywhere, including edge runtimes and container images with no git access.
Only @noble/* for the cryptography. Nothing else to audit or trust.
The receipt viewer checks an Ed25519 receipt live against the public key registry, in the browser, with no server round trip. See drm3.io/verify.
The provenance signing layer beneath all of this has its own page: the Provenance SDK. The receipt every DRM3 product signs, and the one this SDK verifies, is the same object.