Pendle · Rate Limits

Pendle Rate Limits

Pendle V2 API enforces rate limits using a Computing Unit (CU) model. Each endpoint has a fixed or dynamic CU cost. Free accounts are capped at 100 CU/minute and 200,000 CU/week. Paid plans scale from 500 CU/min (Starter, $10/week) up to 2,000 CU/min (Scale, $40/week). The Hosted SDK convert endpoint has dynamic costs based on which aggregators are invoked. Custom aggregator API keys passed via request headers reduce that aggregator's CU cost to zero. Rate limit headers are returned on every response; throttled requests return HTTP 429.

Pendle Rate Limits is the machine-readable rate-limit profile for Pendle on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 8 rate-limit definitions, measuring computing_units_per_minute and computing_units_per_week.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include DeFi, Yield Tokenization, Crypto, and Rate Limiting.

8 Limits Throttle: 429
DeFiYield TokenizationCryptoRate Limiting

Limits

Free tier — per minute api_key
computing_units_per_minute
100
Applies to all endpoints on the free tier.
Free tier — per week api_key
computing_units_per_week
200000
Starter — per minute api_key
computing_units_per_minute
500
Starter — per week api_key
computing_units_per_week
1000000
Growth — per minute api_key
computing_units_per_minute
1000
Growth — per week api_key
computing_units_per_week
2000000
Scale — per minute api_key
computing_units_per_minute
2000
Scale — per week api_key
computing_units_per_week
4000000

Policies

Exponential Backoff
On 429 responses, apply exponential backoff with jitter. Do not poll at fixed intervals.
HTTP Timeouts
Set client HTTP timeout to at least 120 seconds; Hosted SDK convert calls can take several seconds when routing through multiple aggregators.
Pagination
For large datasets use skip/limit parameters and resumeToken. Default page size is 10; maximum is 100. Avoid fetching all pages in rapid succession.
Custom Aggregator Keys
Pass KYBERSWAP-API-KEY, ODOS-API-KEY, OKX-API-KEY, or PARASWAP-API-KEY headers to reduce that aggregator's CU cost to zero.
No Hardcoded Limits
Pendle advises against hardcoding rate limits in client code as limits may change without notice; read limits from response headers dynamically.

Sources

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit 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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/pendle-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.