Lido Finance · Authentication Profile
Lido Finance Authentication
Authentication
Lido's three public REST APIs declare no securitySchemes in their OpenAPI documents and the docs state plainly that "Lido APIs are strictly for read-only access". There are no API keys, no OAuth flows, and no scope surface. The only credentialed surface in the Lido developer stack is The Graph gateway API key required to query the Lido subgraph — that key is issued by The Graph, not by Lido.
Lido Finance declares 0 security scheme(s) across its OpenAPI definitions.
CompanyBlockchainEthereumLiquid StakingDeFiCryptocurrencyStakingWeb3Financial-ServicesGraphQL
Methods:
Schemes: 0
OAuth flows:
API key in:
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
This security artifact
curl "https://apis.io/api/v1/security/lido-finance-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.