Vori Authentication
Every Vori REST API request carries a bearer JWT in the Authorization header. There is no Vori-issued API key or OAuth flow: integrations exchange a Vori user's email/password at Google Identity Toolkit (Firebase identitytoolkit/v3/relyingparty/verifyPassword) for an idToken, then refresh hourly by exchanging the returned refreshToken at securetoken.googleapis.com/v1/token (refresh tokens may rotate on each exchange). Vori recommends creating a banner-level Read-only role user for read-only integrations to limit blast radius.
Vori secures its APIs with http across 1 declared security scheme, 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/vori-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.