Documentation Index
Fetch the complete documentation index at: https://dev.jup.ag/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
All Jupiter APIs use a fixed rate limit based on your plan tier. Rate limits are enforced using a 60-second sliding window.| Tier | Requests per second | Requests per minute | API key required |
|---|---|---|---|
| Keyless | 0.5 | 30 | No |
| Free | 1 | 60 | Yes |
| Developer | 10 | 600 | Yes |
| Launch | 50 | 3,000 | Yes |
| Pro | 150 | 9,000 | Yes |
Rate limits apply per account, not per API key. Creating multiple API keys does not increase your rate limit.
Rate limits are bucketed. Most API requests share the same rate limit bucket. For example, if you are on the Developer plan (10 RPS), a mix of Swap, Price, and Token requests all count towards the same 10 RPS limit. The exceptions are
/swap/v2/execute and /tx/v1/submit, which have their own dedicated buckets (see below).Dedicated rate limit buckets
/execute and /submit each have their own rate limit bucket, separate from the general API limit and from each other. Calls to these endpoints do not count towards your plan’s general RPS quota.
| Tier | RPS per endpoint |
|---|---|
| Keyless | 20 |
| Free | 50 |
| Paid (Developer, Launch, Pro) | 100 |
/execute requests, and 100 /submit requests per second.
Handling rate limits
If you exceed your rate limit, the API returns a429 Too Many Requests response. To handle this:
- Implement backoff: Use exponential backoff in your retry logic
- Spread requests: Distribute requests evenly rather than bursting
- Upgrade your plan: If you consistently hit limits, consider upgrading to a higher tier
Need higher limits?
- See Plans and Pricing to compare tiers
- For limits above 150 RPS, contact us for an enterprise plan
- Visit our support page for further assistance