Cryptographic verification is now live. Govern, attest and mint every check.Go Now

deepidv chain layer

If we verified it,
you can prove it.

Every identity, biometric, document, and address check is minted as a signed envelope, logged in an append-only Merkle tree, and anchored onchain on Base — the only verification stack where every decision is independently verifiable.

Book a demo

DocumentationDeveloper docs

deepidv mints a proof of every check, logs it in a tamper-evident tree, and anchors it onchain — so anyone can verify it, forever.

Envelope hashminted

0x9f4ade21c0b7e8…6d12af83bc04e7a1

Minted at the moment of the check

The instant a check completes, deepidv emits a signed envelope with salted label commitments — never the raw value, at no extra cost or call.

Tree headsealed

root c7a1…e93f

append-only · hourly

Sealed against tampering

Each attestation lands in an append-only RFC 6962 Merkle tree with hourly signed tree heads — a checkpoint proving nothing was inserted or removed.

Onchain anchorverified

Anchored on Baseverify.sh · offline

Verifiable by anyone, forever

Pull the portable proof bundle and confirm it offline, or check the onchain Base anchor from a public RPC — no account, no SDK, no API key.

How It Works

See cryptographic verification in action

Every deepidv check is minted as a signed proof, anchored in public infrastructure and verifiable without trusting any single vendor.

Comprehensive Proof

Every check, minted

The moment a check completes, deepidv mints a signed envelope sealed by the chain-master KMS key — so the result cannot be altered after the fact. Salted commitments record that a check happened without ever exposing who it was about.

What we mint

Signed Verification Envelopes

Sealed by the chain-master KMS key

Salted Label Commitments

A check happened, never the value

RFC 6962 Merkle Leaves

Append-only, million-leaf segments

Hourly Signed Tree Heads

Tamper-evident checkpoints

Onchain Base Anchors

Confirmable from a public RPC

Offline Proof Bundles

Portable, self-contained .dpiv

deepidv chain · mintcomputing

attestation # 1,284,907Minting

envelope

9f4a·de21·c0b7·e8f3

SHA-256(envelope)

b3c1·7af4·9d02·e5b8

salted commitmentLeaf

2d88·a107·fc3e·9144

Merkle leaf #1,284,907Appended

6d12·af83·bc04·e7a1

Signed by chain-master KMS · sealed

Tamper-Evident by Design

Logged, sealed, and anchored onchain

Each attestation is appended to an RFC 6962 transparency log — the same standard that secures the web's certificates — with no edits and no deletions. Every hourly tree head is anchored onchain on Base, fixing the log root in public so no record can be backdated or quietly rewritten.

How a proof is sealed

Append-Only Log

No edits, no deletions, ever

Hourly Tree Heads

Signed tamper-evident checkpoints

Onchain Anchors

Log root fixed in public on Base

Vendor-Independent

Outlives any single provider

RFC 6962 · audit pathverified

Signed tree headHourly

root · c7a1·f209·e93f·8bd4

anchored onchain · Base · tx 0x4d3a…9c2e

hash(A, B)

a8f2·1c09·7e34·bb56

sibling leaf

f703·b8c2·5d91·4e0a

hash(leaf, sibling)

4c7e·9201·d3f8·a65b

leaf #1,284,907Proven

6d12·af83·bc04·e7a1

Append-only · no edits, no deletions

Two Ways to Verify

Verify it yourself

Move from trust our dashboard to verify it yourself. Look up any attestation in the live registry and confirm the onchain anchor from a public RPC, or download a portable bundle and run verify.sh fully offline — disputes settled by math, not a support ticket.

What every proof includes

Signed Envelope Hash

Fingerprint sealed by the chain key

Dual RFC 3161 Timestamps

Two independent authorities

Merkle Audit Path

Proof it sits in the log

Onchain Anchor Reference

Confirm the root on Base

Read the docs

verify.sh · offline runproof verified

$verify.sh attestation-1284907.dpiv

·loading bundle … ok

✓envelope sig 9f4ade21…e7a1

✓Merkle path leaf → root c7a1

✓onchain anchor Base tx 0x4d3a…9c2e

→PROOF VERIFIED

Offlineverify.sh · no account

OnchainBase · public RPC

verify.deepidv.com/p/1284907Public

Trusted & Certified

Built to meet the world's most demanding security and privacy standards.

SOC 2 Type II

Audited security controls for data protection

GDPR Compliant

Full compliance with EU data privacy regulations

ISO 27001

International standard for information security

DIACC Member

Digital ID & Authentication Council of Canada

Integration

Take full control.
Getting started takes minutes.

Plug deepidv into your stack three ways — a REST API, native SDKs, or an MCP server your AI agents can call directly. Clean docs, a sandbox, and one source of truth take you from API key to live verification the same day.

REST API

Call any verification service directly — create a session or run a standalone check and get structured JSON back in under 500ms.

→ screening 200+ watchlists…
✓ status: clear
  risk_score: 4 · 143ms

Drop-in SDK

Pre-built UI components and server libraries for iOS, Android, Web, Node, Python, and Go — zero to live verification in a single sprint.

  checks: ['id','liveness','face'],
✓ v.url → send to your user

MCP for agents

An open protocol that lets any AI agent call deepidv's verification engine directly — no custom integration code. Connect it in one command.

Claude

Launch deepidv for my AI agent — set it up from the docs.

✓ 12 verification tools available

Ready to run ID, liveness & AML checks.

Changelog

The Latest

See all releases

May 18, 2026Release

Verify 2.0 is here

Multi-language verification, a redesigned ID & face-capture flow, end-to-end whitelabel, and a native Background Check step.

May 9, 2026Features

ProofCall, smoother capture & translated reports

AI background-confirmation calls, faster camera start-up, translated PDF/HTML reports, and location-by-IP enrichment.

April 10, 2026AI

AI-powered adverse media screening

Continuous, AI-driven adverse-media checks built natively into your verification workflows.

See all releases

Frequently asked questions

It is the proof layer beneath every deepidv check. Each identity, biometric, document, and address verification is minted as a signed envelope, logged in an append-only RFC 6962 Merkle tree, and anchored onchain on Base. The result is a verification you can prove independently, without trusting deepidv, your vendor, or a private database.

No. The transparency log records a salted commitment to each label, never the underlying value, so a proof confirms that a check happened without revealing who it was about. It is privacy-preserving by design, no identities, just proofs, with zero PII written to the log.

Every attestation ships as a portable bundle containing the signed envelope hash, RFC 3161 timestamps from two independent authorities, the Merkle audit path, and the signed tree head. You can run verify.sh against any .dpiv bundle on your own machine, with no SDK, no account, and no API key, or confirm the onchain anchor from any public Base RPC.

Anchoring fixes the log root in public so it cannot be quietly rewritten. Each hourly signed tree head is committed onchain, which means anyone can confirm the state of the transparency log from a public RPC and a downloaded proof bundle, making the record tamper-evident and vendor-independent.

No. Minting is automatic and built into every verification through the deepidv API and SDK, at no extra cost and with no extra call. The proofs are public in the registry and transparency log, and the verification tools are open via @deepidv/chain on npm and deepidv-chain on pip.

Still have questions?

Our team is ready to help you get started.

Contact Sales

All-In-One Products

Explore the Full Suite

AI Document Verification

NFC Verification

Chain Verification

Face Liveness

1:N Biometric Matching

If we verified it, you can prove it.

See deepidv mint and anchor verifiable proof of every check — it takes 60 seconds to start.

Get Started View API Docs

If we verified it,
you can prove it.