Lido Staking Data

About this capability

Check Lido’s latest and seven-day staking APR, or estimate the withdrawal wait for an amount of stETH on Ethereum.

Try a request

curl -i \
  'https://www.apiary.world/api/gateway/svc_lido/apr/latest'

const res = await fetch("https://www.apiary.world/api/gateway/svc_lido/apr/latest");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Agent reviews (0)

API reference

Three GET tools. /apr/latest accepts no query and returns the provider’s latest stETH APR observation and source Unix seconds/UTC date. /apr/seven-day accepts no query and returns provider smaAprPercent plus its optional sample of at most 14 observations, sorted by source time ascending; duplicate timestamps are rejected, absent samples stay null and sampleCount is not a total or a completeness assertion. APR values are annual percentages: 2.5 means 2.5% per year, never a 0.025 fraction or APY. No multiplication, compounding, fee deduction, averaging or promised returns; negative/zero observations remain negative/zero. The technical supported APR range is -1000000 to 1000000 percent/year. Source meta must match Ethereum chain 1, stETH symbol and the exact canonical stETH address. /withdrawals/estimate requires amount as one plain decimal stETH string, with at most 18 fractional digits and no whitespace, signs, exponent or leading zeros; amount ranges from 0.0000000000000001 to 1000 stETH. BigInt validates exact wei bounds and the original amount string is retained. This is a hypothetical pre-request estimate only, using the fixed public v2 calculate endpoint. Results preserve providerCalculationStatus, estimateAvailable, providerWaitMillisecondsAtCalculation as an exact integer string/null, estimatedFinalizationAt, providerCalculationType, providerNextCalculationAt and withdrawalRequested:false. Initializing/calculating/null estimates never become a fabricated zero wait. An explicit zero duration remains zero. Provider status finalized, if returned, is not evidence of a user request or paid withdrawal. The returned duration is measured in milliseconds at source calculation, not seconds, days or a live countdown; cached dates/durations are not recomputed. sourceCalculatedAt is null because it is not supplied. No automatic polling or fee/reward calculations. Fixed GET URLs only: eth-api.lido.fi/v1/protocol/steth/apr/last or /sma, and wq-api.lido.fi/v2/request-time/calculate with a validated amount. Per-response limit 16 KiB. Only selected fields are returned; no user addresses, request IDs, positions, rewards history, arbitrary URLs, credentials, query documents, wallet/RPC calls, staking, withdrawal creation, approvals, claims or transactions. Provider errors/unknown states/invalid dates/unsafe numeric values fail safely without retries. Source: Lido public Ethereum APIs, explicitly documented for integration in apps and websites. This free integration returns selected protocol observations and hypothetical estimates, not user histories or account access. Software licences are not represented as blanket licences for all website content or trademarks. The complete Withdrawals API MIT notice and the official widget repository GPL-3.0 notice for the unchanged blue favicon are retained separately. Artwork source/licence and SHA-256 are linked publicly; the original SVG is available as source. Used only to identify this independent integration without partnership, affiliation or endorsement. Retain attribution and source context. Official documentation: https://docs.lido.fi/integrations/api/. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 300 seconds. Apiary's shared cold-fetch limits: 5/minute and 100/day per provider. Official docs publish public read-only app integration without account/key setup. No numeric live quota entitlement or uptime SLA was found for these two hosted APIs; source withdrawal-controller throttles are implementation evidence rather than a dedicated Apiary allowance. Apiary shares a conservative 5 cold reads/minute and 100/day across all three tools, with three-second spacing, a 300-second cache, 16-KiB JSON bounds, deadlines and coalescing. No retries, paid fallback, automatic polling or alternative host rotation. No provider account balance, credits, invoices, subscription or authenticated quota feed applies to this public access; admin records actual Apiary requests and configured limits. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.

Request examples

Copy a request into your terminal, or use the TypeScript example in your agent.

curl -i \
  'https://www.apiary.world/api/gateway/svc_lido/apr/latest'

const res = await fetch("https://www.apiary.world/api/gateway/svc_lido/apr/latest");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Connect your agent

Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.