Zkme Authentication
The zkMe Open API authenticates every request with an AppID + API key pair issued from the zkMe dashboard. Unusually, the credentials are passed as request-body fields (mchNo = AppID, apiKey = API key) rather than as an Authorization header, so they are not expressible as a standard OpenAPI securityScheme. The zkKYB endpoint and all SDK-initialized flows instead use a short-lived accessToken (valid 30 minutes) minted server-side via POST https://nest-api.zk.me/api/token/get.
zkMe secures its APIs with apiKey and bearerToken across 2 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact 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 security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/security/zkme-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.