Skip to Content

An open credential-verification protocol

Issue once. Verify anywhere, instantly.

Attest ID lets institutions sign W3C Verifiable Credentials that anyone can verify cryptographically — no registry lookup, no phone call to the registrar, no PDF to squint at. Built on open standards only: W3C Verifiable Credentials, DID, Ed25519. No proprietary format, no vendor lock-in, no blockchain dependency.

QuickstartSystem designAPI & gRPC reference

The problem this protocol solves

950M+
credentials issued globally every year
TodayVerified by phone calls to registrars and scanned PDFs.
Attest IDInstant, cryptographic, cross-border verification.

How a request flows

Core Engine is the only service that knows this whole shape — the anti-corruption layer that keeps the Gateway and every microservice from ever learning about one another. Full service list, ports, and proto contracts in System Design.

Find your surface

Issuerissuer-portalInstitutions issuing and managing credentialsOnboard an issuer →
Holdercredential-walletPeople holding, sharing, and controlling access to their credentialsAuth model →
Verifierverifier-portalEmployers and registered verifiers checking authenticityVerifier identity →
Custodiancustodian-portalOrganizations bulk-attesting to documents they collected but didn’t issueCustodian model →
Adminadmin-consolePlatform operators: issuer approval, catalog, system healthRun it locally →

Go deeper

The problem, the standards it’s built on, and the design principles behind every decision.

What is Attest ID

How a credential’s provenance survives intake, holder claim, and cross-custodian handoff.

Chain of custody

The W3C VC JSON shape, gRPC message contracts, and Ed25519 verification, in code.

Data models & crypto