zkMe

zkMe is a decentralized identity network delivering privacy-preserving compliance for Web3. Using zero-knowledge proofs, self-sovereign identity (SSI) wallets, DID methods and soulbound tokens, zkMe lets applications verify their users and businesses without ever handling raw personal data. Its product suite spans zkKYC (customer identity with sanction, age, citizenship, location and uniqueness/anti-Sybil proofs), zkKYB (business entity and UBO verification), zkOBS (open-banking proof of accredited investor and proof of address), and KYT (on-chain wallet-address and transaction risk screening). Verification runs client-side through embeddable JavaScript and mobile widgets; integrators then query outcomes through the zkMe Open API on agw.zk.me using an AppID + API key pair. zkMe also publishes zkTLS verifier SDKs, DID registry/resolver tooling and smart contracts through its zkMeLabs GitHub org.

zkMe publishes 5 API contracts indexed on the APIs.io network, including Auth API, KYT API, zkKYB API, and 2 more. Tagged areas include Company, Web3, Identity, KYC, and KYB.

The zkMe catalog on APIs.io includes 1 Spectral governance ruleset.

zkMe’s developer surface includes documentation, API reference, getting-started guide, signup flow, support, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

32.8/100 thin ▬ flat Agent 26/100 agent aware Front door AI 6/6 dominant Heartbeat 56/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 3 Agent Skills

Company Web3 Identity KYC KYB Compliance Zero Knowledge Decentralized IdentityAnti-SybilTransaction Monitoring

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 32.8/100 · thin

Contract Quality 2.2 / 19

Developer Ergonomics 9.6 / 15

Access Clarity 0.0 / 15

Operational Transparency 3.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.4 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 26/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/zkme/"><img src="https://apis.io/badge/zkme/card.svg" alt="zkMe on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 11.9 — up to +22.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/zkme/apis.yml: open an issue on github.com/api-evangelist/zkme to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	distribution	9.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

zkMe Auth API

Access-token issuance for SDK integration

zkMe KYT API

Know-Your-Transaction wallet-address and transaction risk screening

zkMe zkKYB API

Business entity and UBO verification status

zkMe zkKYC API

Customer identity verification results and proofs

zkMe zkOBS API

Open banking / accredited-investor (proof of accreditation)

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

zkMe Protocol Auth API

OPEN COLLECTION

zkMe Protocol Auth KYT API

OPEN COLLECTION

zkMe Protocol Auth zkKYB API

OPEN COLLECTION

zkMe Protocol Auth zkKYC API

OPEN COLLECTION

zkMe Protocol Auth zkOBS API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Check a business zkKYB verification status

AGENT SKILL

Screen a wallet address for risk (KYT)

AGENT SKILL

Check a user's zkKYC status

AGENT SKILL

Rate Limits 1

Documented rate limits and quota policies.

Zkme Rate Limits

1 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

zkMe API Rules

53 rules · 50 errors 1 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Zkme Openapi Overlay

3 actions · update · zkme-openapi.yml

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Zkme Authentication

apiKey/bearerToken · 2 schemes

SECURITY

Zkme Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Zkme Vulnerability Disclosure

Hackerone · contact published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Zkme Agentic Access

14 operations · 1 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgenticAccess

AgentSkill

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Components

Components

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Company 2

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: zkme
name: zkMe
description: zkMe is a decentralized identity network delivering privacy-preserving compliance for Web3. Using zero-knowledge
  proofs, self-sovereign identity (SSI) wallets, DID methods and soulbound tokens, zkMe lets applications verify their users
  and businesses without ever handling raw personal data. Its product suite spans zkKYC (customer identity with sanction,
  age, citizenship, location and uniqueness/anti-Sybil proofs), zkKYB (business entity and UBO verification), zkOBS (open-banking
  proof of accredited investor and proof of address), and KYT (on-chain wallet-address and transaction risk screening). Verification
  runs client-side through embeddable JavaScript and mobile widgets; integrators then query outcomes through the zkMe Open
  API on agw.zk.me using an AppID + API key pair. zkMe also publishes zkTLS verifier SDKs, DID registry/resolver tooling and
  smart contracts through its zkMeLabs GitHub org.
url: https://raw.githubusercontent.com/api-evangelist/zkme/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://zk.me/favicon.ico
x-type: company
x-source: vc-portfolio
x-backed-by:
- multicoin-capital
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Web3
- Identity
- KYC
- KYB
- Compliance
- Zero Knowledge
- Decentralized Identity
- Anti-Sybil
- Transaction Monitoring
tags_raw:
- Company
- Crypto Web3
- Identity
- KYC
- KYB
- Compliance
- Zero Knowledge
- Decentralized Identity
- Anti-Sybil
- Transaction Monitoring
- Web3
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: zkme:zkme-auth-api
  name: zkMe Auth API
  description: Access-token issuance for SDK integration
  humanURL: https://docs.zk.me/hub/start/onboarding/integration/api
  baseURL: https://agw.zk.me
  tags:
  - Authentication
  tags_raw:
  - Auth
  properties:
  - type: OpenAPI
    url: openapi/zkme-auth-api-openapi.yml
  - type: Authentication
    url: authentication/zkme-authentication.yml
  - type: Conventions
    url: conventions/zkme-conventions.yml
  - type: Idempotency
    url: conventions/zkme-conventions.yml
  - type: ErrorCatalog
    url: errors/zkme-problem-types.yml
  - type: DataModel
    url: data-model/zkme-data-model.yml
  - type: RateLimits
    url: rate-limits/zkme-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/zkme-lifecycle.yml
  - type: Conformance
    url: conformance/zkme-conformance.yml
- aid: zkme:zkme-kyt-api
  name: zkMe KYT API
  description: Know-Your-Transaction wallet-address and transaction risk screening
  humanURL: https://docs.zk.me/hub/start/onboarding/integration/api
  baseURL: https://agw.zk.me
  tags:
  - Transaction Monitoring
  tags_raw:
  - KYT
  properties:
  - type: OpenAPI
    url: openapi/zkme-kyt-api-openapi.yml
  - type: Authentication
    url: authentication/zkme-authentication.yml
  - type: Conventions
    url: conventions/zkme-conventions.yml
  - type: Idempotency
    url: conventions/zkme-conventions.yml
  - type: ErrorCatalog
    url: errors/zkme-problem-types.yml
  - type: DataModel
    url: data-model/zkme-data-model.yml
  - type: RateLimits
    url: rate-limits/zkme-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/zkme-lifecycle.yml
  - type: Conformance
    url: conformance/zkme-conformance.yml
- aid: zkme:zkme-zkkyb-api
  name: zkMe zkKYB API
  description: Business entity and UBO verification status
  humanURL: https://docs.zk.me/hub/start/onboarding/integration/api
  baseURL: https://agw.zk.me
  tags:
  - zkKYB
  properties:
  - type: OpenAPI
    url: openapi/zkme-zkkyb-api-openapi.yml
  - type: Authentication
    url: authentication/zkme-authentication.yml
  - type: Conventions
    url: conventions/zkme-conventions.yml
  - type: Idempotency
    url: conventions/zkme-conventions.yml
  - type: ErrorCatalog
    url: errors/zkme-problem-types.yml
  - type: DataModel
    url: data-model/zkme-data-model.yml
  - type: RateLimits
    url: rate-limits/zkme-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/zkme-lifecycle.yml
  - type: Conformance
    url: conformance/zkme-conformance.yml
- aid: zkme:zkme-zkkyc-api
  name: zkMe zkKYC API
  description: Customer identity verification results and proofs
  humanURL: https://docs.zk.me/hub/start/onboarding/integration/api
  baseURL: https://agw.zk.me
  tags:
  - zkKYC
  properties:
  - type: OpenAPI
    url: openapi/zkme-zkkyc-api-openapi.yml
  - type: Authentication
    url: authentication/zkme-authentication.yml
  - type: Conventions
    url: conventions/zkme-conventions.yml
  - type: Idempotency
    url: conventions/zkme-conventions.yml
  - type: ErrorCatalog
    url: errors/zkme-problem-types.yml
  - type: DataModel
    url: data-model/zkme-data-model.yml
  - type: RateLimits
    url: rate-limits/zkme-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/zkme-lifecycle.yml
  - type: Conformance
    url: conformance/zkme-conformance.yml
- aid: zkme:zkme-zkobs-api
  name: zkMe zkOBS API
  description: Open banking / accredited-investor (proof of accreditation)
  humanURL: https://docs.zk.me/hub/start/onboarding/integration/api
  baseURL: https://agw.zk.me
  tags:
  - zkOBS
  properties:
  - type: OpenAPI
    url: openapi/zkme-zkobs-api-openapi.yml
  - type: Authentication
    url: authentication/zkme-authentication.yml
  - type: Conventions
    url: conventions/zkme-conventions.yml
  - type: Idempotency
    url: conventions/zkme-conventions.yml
  - type: ErrorCatalog
    url: errors/zkme-problem-types.yml
  - type: DataModel
    url: data-model/zkme-data-model.yml
  - type: RateLimits
    url: rate-limits/zkme-rate-limits.yml
  - type: Lifecycle
    url: lifecycle/zkme-lifecycle.yml
  - type: Conformance
    url: conformance/zkme-conformance.yml
common:
- type: RateLimits
  url: rate-limits/zkme-rate-limits.yml
- url: https://blog.zk.me/rss/
  type: BlogRSS
- type: X-MCPServerCandidate
  url: mcp/zkme-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/zkme-openapi-overlay.yaml
- type: AgenticAccess
  url: agentic-access/zkme-agentic-access.yml
- type: DomainSecurity
  url: security/zkme-domain-security.yml
- type: Website
  url: https://zk.me
- type: DeveloperPortal
  url: https://docs.zk.me
- type: Documentation
  url: https://docs.zk.me/hub/start/onboarding
- type: APIReference
  url: https://docs.zk.me/hub/start/onboarding/integration/api
- type: GettingStarted
  url: https://docs.zk.me/hub/start/onboarding
- type: GitHubOrganization
  url: https://github.com/zkMeLabs
- type: SignUp
  url: https://dashboard.zk.me
- type: Support
  url: https://docs.zk.me
- type: Packages
  url: packages/zkme-packages.yml
- type: SDKs
  url: packages/zkme-packages.yml
- type: Components
  url: components/zkme-components.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/zkme-llms.txt
- type: VulnerabilityDisclosure
  url: security/zkme-vulnerability-disclosure.yml
- type: Security
  url: https://docs.zk.me/hub/explore/bounty
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 21
  pass: local-v1

zkMe API — frequently asked questions

Does zkMe have an API?

Yes. APIs.io lists 5 APIs from zkMe, including zkMe Auth API, zkMe KYT API and zkMe zkKYB API, and 2 more.

Is there an OpenAPI specification for the zkMe API?

Yes. APIs.io indexes 5 OpenAPI specifications for zkMe, each linked for download from this page.

How do I authenticate with the zkMe API?

zkMe uses bearer-token authentication (apiKey/bearerToken · 2 schemes). The details are profiled on APIs.io as Zkme Authentication.

Is the zkMe API ready for AI agents?

zkMe has a Kin Score of 32.8 out of 100 (thin) and an Agent Readiness score of 26.2 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/zkme"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/zkme/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/zkme/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.