Summary: zkMe is a reusable zero-knowledge identity and compliance platform whose current official materials now reach well beyond a simple KYC widget. The docs describe a broader architecture spanning a dedicated identity chain, a privacy-preserving credential system, zkTLS/open-banking proofs, KYB and AML products, and an Agent Trust Gateway for AI-agent authorization and execution. It is best cataloged as identity and open-finance infrastructure for the emerging agent economy rather than as only a compliance SaaS vendor.
What it does:
Offers reusable verification products including zkKYC, zkAML, zkKYB, zkOBS open-banking proofs, proof-of-personhood, proof-of-citizenship, proof-of-location, proof-of-address, and financial/account proofs
Runs a credential system built around W3C-style verifiable credentials, selective disclosure, reusable credentials, multi-credential proofs, anti-sybil/nullifier mechanisms, and agent-ready credentials
Documents a zkMe Identity Chain, an EVM-compatible identity-focused Layer 1 with storage providers, DID registries, credential-state anchoring, and cross-chain verification support
Builds an Agent Trust Gateway that uses TEE execution, credential verification, policy evaluation, human-in-the-loop approval, scoped token issuance, and audit logging for AI-agent actions
Exposes JS/mobile SDKs, widget integrations, dashboard flows, APIs, smart contracts, and supported-protocol docs for MCP, x402/AP2, OIDC4VP, and related integrations
Key claims:
The homepage frames zkMe as reusable zero-knowledge KYC for the agentic economy, with one credential reused across 90+ platforms, support for 15+ chains, and a no-PII yes/no verification model
The architecture overview describes zkMe as a decentralized, permissionless, composable zk-identity layer using ZKPs, FHE, MPC, and zkTLS, organized around Secure, Underwrite, and Gate pillars
The credential-system docs say the stack is designed so holders prove claims without revealing raw data, while issuers, holders, and verifiers retain clear audit and liability boundaries anchored to blockchain state
The identity-chain docs claim a purpose-built identity Layer 1 with CometBFT-based Proof-of-Stake, EVM compatibility via EVMOS, approximate 1-second blocks, instant finality, and storage-provider support for residency-sensitive encrypted credential data
The Agent Session Flow docs describe an 8-step TEE-mediated execution path where agents submit delegated credentials, pass policy checks, receive scoped session context, and leave an immutable audit trail without ever holding raw user secrets
The docs hub and llms.txt show an unusually broad current product surface that includes identity, compliance, open banking, agent trust, and open-finance primitives rather than a narrow KYC-only product
Whitepaper: No canonical standalone zkMe whitepaper or litepaper surfaced in this pass. The docs hub, architecture pages, credential-system docs, agent-trust docs, and source repositories appear to be the clearest current source of truth; see ../whitepapers/zkme-primary-sources-2026-04-27.md.