Lido
Lido is the leading liquid staking protocol on Ethereum, allowing anyone to stake ETH without locking it or running validator infrastructure. Stakers deposit ETH and receive stETH — a rebasing ERC-20 that earns daily staking rewards — or its non-rebasing wrapped form wstETH used widely across DeFi. Lido is governed by the Lido DAO via the LDO token, Snapshot signaling, on-chain Aragon voting, and a Dual Governance timelock that gives stETH holders a dynamic veto over the DAO. The protocol's validator set is delegated across multiple Staking Modules — the Curated Module (professional node operators), Simple DVT (distributed validator technology via Obol and SSV), the Community Staking Module (permissionless solo stakers backed by bonded stETH), and stVaults (modular tailored setups). At over $18B TVL and 8.8M+ ETH staked, Lido is the #1 liquid staking provider by total value locked. Lido previously operated on Polygon (stMATIC, sunset June 2025) and Solana (stSOL, sunset February 2024); the protocol is now Ethereum-only. Lido publishes the open-source core smart contracts, a TypeScript SDK (`@lidofinance/lido-ethereum-sdk`), a Python oracle daemon, validator monitoring tooling, frontend widgets, and three public read-only HTTP APIs for protocol APR, reward history, and withdrawal queue timing.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Lido the way a machine reads it — 24 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lido scores 27.9/100 (thin), with a separate agent-readiness read of 13/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Lido's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lido/"
title="Lido on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lido.svg"
alt="Lido Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/lido/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/lido/"
title="Lido on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/lido/card.svg"
alt="Lido Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Lido
Each block below is one kind of artifact we hold for Lido. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lido APR API
Read-only HTTP API returning the latest stETH staking APR and a 7-day simple moving average APR. Used by integrators, dashboards, and DeFi protocols to display Lido's current an...
Lido Reward History API
Read-only HTTP API returning a per-address stETH reward history including USD/EUR/GBP fiat conversions, with options to filter to rewards-only, sort, paginate, and choose archiv...
Lido Withdrawals API
Read-only HTTP API for the Lido stETH withdrawal queue. Returns estimated finalization times for one or more withdrawal request IDs, and can forecast the expected wait time for ...
Lido Keys API
Service that exposes node operator validator keys from each Lido staking module (Curated, Simple DVT, CSM) for use by deposit security infrastructure, validator monitoring, and ...
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Lido Finance GraphQL API
Lido Finance exposes on-chain protocol data through a subgraph on The Graph protocol. The subgraph indexes Ethereum mainnet events from the Lido stETH contract, the Withdrawal Q...
GRAPHQLFeatures 17
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 17 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Lido — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 9
Reference material describing how the API behaves
Scroll within the panel for all 9 ·
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 16
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 16 ·
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 15
Properties that don't map to a standard resource type
Scroll within the panel for all 15 ·
← All providers · Data indexed from github.com/api-evangelist/lido · machine-readable index on apis.io
This is an independent, third-party profile of Lido, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.