Pverify Authentication
pVerify uses a two-factor-by-header model: an OAuth2 client-credentials bearer token obtained from POST /Token, sent alongside a Client-API-Id header that identifies the account. Both are required on every call. A small set of "one step" endpoints skips the token entirely and authenticates with Client-API-Id + Client-Secret headers, and one endpoint (GetPayerStatus) is documented as requiring no authentication at all.
pVerify secures its APIs with http and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).
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/pverify-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.