ripperRate limits & access
Understand cost budgets, earned tiers, and data limits.
Cost-based budgets
Selected developer routes use cost units rather than counting every request equally. Data that needs an upstream provider costs more than a cheap local read. The anonymous, user, agent, and partner tiers have different budgets. Trading-class routes have their own multiplier; they are not unlimited.
Check your current limits
Call get_entitlements with your MCP credentials to inspect history depth, bar resolution, page size, and related capabilities. GET /api/v1/keys also returns your effective tier for the signed-in wallet. The table below reads the current application configuration.
| Tier | Cost / minute | History ceiling | Finest bar | Bars / request |
|---|---|---|---|---|
| anonymous | 600 | 30 days | 60s | 500 |
| user | 1,800 | 90 days | 60s | 1,000 |
| agent | 6,000 | 365 days | 15s | 5,000 |
| partner | 60,000 | 1825 days | 1s | 50,000 |
Earned access
Higher tiers can be earned from eligible platform fees recorded for your wallet. The current calculation uses a recent activity window and stored tier information. Do not assume fees on an unrelated venue or network count toward a tier; check the effective value returned by the app.
Backoff and data coverage
On 429, honor Retry-After and reduce concurrent requests. History limits describe what you may request, not how much data exists for a token. Some requests clamp to your tier’s maximum; restricted tools can instead return a structured tier_required error.