VerifyLink Infrastructure

Built on VLI.

Five live products running on this infrastructure today. Every event sealed, every receipt registered, every action verifiable by anyone with ClearKey.

Pact

Provable agreements for any deal.

From notarized contracts to inter-org deal sealing — every signature, witness, and version cryptographically tied to identity. Replaces faxes, DocuSign, and notaries with math.

Seal · Register · Verify · Vault Visit →

WorkSpaces

Compliance as a side effect of running your org.

Sealed inventory, attested check-ins, immutable audit trail, AI registry — the org OS where every action becomes evidence.

TapIn

Verified arrivals, signed in real time.

Patients, attendees, members — biometric tap-in produces a sealed receipt, no shared databases, no spoofable badges.

Origin

Cryptographic proof of authorship.

Drop a file, get a sealed timestamped receipt anchored to the VLI registry. IP priority and creative attribution that holds up in court.

ART

The public registry of AI agents.

Discover, attest, and verify AI agents and their delegated capabilities — VLI's transparency layer for AI accountability.

Same primitives, different domains.

These five products look nothing alike. A contract platform, an org OS, a check-in app, a proof-of-creation tool, and an AI registry. But under the hood they all run on the same four primitives.

That's the point of infrastructure: one math layer, infinite product shapes.

Seal · Register · Verify · Vault

What you could build on VLI.

These are categories we know the infrastructure supports. The math is already there. Someone just has to build it.

Chain of custody

Courier handoffs, evidence transport, controlled-substance shipments. Every node a sealed event, every hand-off attested.

Why VLI fits this
Each handoff = ai_seal_event with previous bundle hash → tamper-evident transport chain anchored to public registry.

Sealed records for regulated industries

Medical records, legal filings, financial disclosures. Tamper-evident from creation, portable across vendors.

Why VLI fits this
Document → JCS canonicalization → Ed25519 sign → Merkle inclusion → portable bundle with no vendor lock-in.

High-value P2P transactions

Real estate, used vehicles, art sales. Identity-attested, multi-party signed, registry-anchored — without the title company.

Why VLI fits this
Multi-party Pact-style bundles with co-signed Ed25519 attestations + ART agent attestations for KYC.

Identity-bound personal archives

Family medical history, wills, legacy data. Sealed at creation, verifiable across decades, no platform lock-in.

Why VLI fits this
SAPI-bound seal + long-term Vault preservation + ClearKey verifiable forever.

Verifiable media

Photos, video, audio sealed at the moment of capture. Provenance-by-default for journalism, evidence, citizen reporting.

Why VLI fits this
Capture device signs raw bytes → seal anchored to registry → C2PA-compatible bundle with VLI proof.

AI-assisted workflows requiring receipts

Any system where an AI took an action and you need to prove what, when, and on whose authority later.

Why VLI fits this
mcp-ai-trust ai_begin_session → ai_seal_decision per call → ai_end_session → registry-anchored audit bundle.

Building something new?

ClearKey CLI verifies any seal locally. The MCP servers expose VLI infrastructure to your agents. Registry API anchors your bundles to public transparency. SAPI handles identity. Start with what's already there.