Cowrie Research

zkme-primary-sources-2026-04-27

4 min read

zkMe primary-source snapshot

Fetched: 2026-04-27 UTC

1) Core identity: reusable zero-knowledge credentials for the agent economy

Source: https://www.zk.me/ Source: https://docs.zk.me/hub/zkme-protocol.md

Selected excerpts from the official materials:

Reusable Zero-Knowledge KYC for the Agentic Economy

One protocol: identity, business, transaction, finance, and AI agents.

Additional signals from the official materials:

  • The homepage presents zkMe as broader than a one-time KYC flow, with reusable credentials and support across multiple chains and counterparties
  • The docs hub confirms that the live product surface spans identity, business verification, finance, open banking, and agent workflows
  • This is a strong sign that zkMe should be cataloged as reusable credential infrastructure, not just a compliance form factor

2) Architecture: Secure / Underwrite / Gate

Source: https://docs.zk.me/hub/how-works/architecture.md

Selected excerpts from the official materials:

zkMe Protocol is a decentralized, permissionless, and composable zk-Identity Layer designed to unify, standardize, and process digital identities across all ecosystems, spanning all chains and Web2 environments.

As zkMe evolves into the Identity and Open Finance Kernel for the Agent Economy, its architecture is organized around three core pillars: Secure, Underwrite, and Gate.

Additional signals from the docs:

  • The architecture is unusually explicit about how identity infrastructure, credential verification, and AI-agent execution fit together
  • Secure covers SSI, DID, zkVault, FHE, zkPassport, zkTLS, and smart contracts; Underwrite covers the credential system; Gate covers the Agent Trust Gateway
  • This makes zkMe look like a broader identity/open-finance kernel rather than a narrow KYC provider

3) Credential system and compliance model

Source: https://docs.zk.me/hub/how-built/credential-sys/core-concepts.md Source: https://docs.zk.me/hub/zkme-protocol.md?ask=What%20products%2C%20supported%20verification%20flows%2C%20integration%20surfaces%2C%20and%20whether%20the%20docs%20link%20a%20whitepaper%20or%20litepaper%20are%20documented%3F

Selected excerpts from the official materials:

The Credential System is a decentralized, privacy-preserving credential issuance and verification infrastructure built on zero-knowledge proof (ZKP) technology.

The system is architected so that the Holder never reveals raw data to the Verifier. Only the proof of a specific claim is shared.

Additional signals from the docs:

  • The docs define clear issuer / holder / verifier responsibility boundaries and on-chain auditability without raw-data exposure
  • The accessible product surface includes zkKYC, zkAML, zkKYB, zkOBS, proof-of-citizenship, account-ownership and transaction-history proofs, and agent-specific credential products
  • Integration surfaces include widget/JS SDK, mobile SDK, API, smart contracts, dashboard, MCP, x402/AP2, OIDC4VP, and PASETO-linked agent flows

4) Identity chain and infrastructure substrate

Source: https://docs.zk.me/hub/how-built/id-infra/zkme-identity-chain.md

Selected excerpts from the official materials:

The zkMe Identity Chain is a Layer 1 EVM-compatible blockchain purpose-built for decentralized identity.

The zkMe Identity Chain addresses this by providing instant finality, sub-second block times, and a purpose-built storage layer optimized for identity payloads.

Additional signals from the docs:

  • zkMe documents a dedicated identity chain instead of relying only on third-party chains for trust anchoring
  • The chain is described as CometBFT-based with EVM compatibility, storage-provider support, DID registries, and residency-sensitive encrypted credential storage
  • This is a major categorization clue that pushes zkMe toward infrastructure rather than pure SaaS compliance middleware

5) Agent Trust Gateway

Source: https://docs.zk.me/hub/how-built/agent-trust-gateway/agent-session-flow.md

Selected excerpts from the official materials:

The flow ensures that the Agent can execute its tasks seamlessly while the User retains absolute control and visibility over their identity and assets.

The Agent never possesses the raw user credentials or private keys.

Additional signals from the docs:

  • The 8-step session flow is concrete enough to recover the trust model: delegated credentials, TEE ingress, credential verification, policy evaluation, optional human approval, scoped token/ZKP issuance, proxied execution, and immutable audit logging
  • This makes the “agent economy” framing operational rather than purely marketing language

6) Whitepaper status

Source: https://docs.zk.me/hub/llms.txt Source: https://docs.zk.me/hub/zkme-protocol.md?ask=What%20products%2C%20supported%20verification%20flows%2C%20integration%20surfaces%2C%20and%20whether%20the%20docs%20link%20a%20whitepaper%20or%20litepaper%20are%20documented%3F

Notes:

  • In this pass, no canonical standalone whitepaper or litepaper link surfaced from the accessible docs pages.
  • The docs hub itself appears to be the current source of truth.

Notes

  • zkMe appears best cataloged as privacy-preserving identity and compliance infrastructure / reusable zero-knowledge credential network / agent trust gateway.
  • The key categorization clue is the combination of reusable credentials, a dedicated identity chain, and TEE-mediated agent authorization/execution.
  • The official materials now describe a meaningfully broader product and protocol surface than a simple reusable KYC widget.

Graph View