Rate Limits & Credits
Renidly meters traffic on two axes — credits (billing) and a per-minute rate limit (throughput). Both move with your tier. The higher your balance, the higher your allowance and the cheaper each credit gets.
How tiers work
Every workspace sits in exactly one tier, decided by its current credit balance. As you spend or top up credits and cross a tier boundary, four things change in lockstep:
- Per-minute rate limit — how many calls you're allowed in any 60-second window.
- Price per credit — higher tiers buy more credits per dollar.
- Tier name — surfaced in the dashboard, the Tier endpoint, and your invoices.
- Headroom — how many credits you can still consume before dropping to the tier below.
The full tier table
9 tiers, from entry-level evaluation up to a custom strategic partner band. Per-tier dollar math mirrors the dashboard topup page exactly — no re-derivation, no drift.
| # | Tier | Credit range | Rate limit | Credits / $ | $ / 1k credits | Min $ to enter |
|---|---|---|---|---|---|---|
| Testing | 0 – 99 | 7 / min | 100 | $10.00 | Free | |
| Hobby | 100 – 9,999 | 30 / min | 120 | $8.33 | $1 | |
| Developer | 10,000 – 29,999 | 70 / min | 185 | $5.41 | $55 | |
| Startup | 30,000 – 59,999 | 90 / min | 210 | $4.76 | $143 | |
| Growth | 60,000 – 99,999 | 150 / min | 270 | $3.70 | $223 | |
| Scale | 100,000 – 299,999 | 250 / min | 345 | $2.90 | $290 | |
| Business | 300,000 – 599,999 | 350 / min | 355 | $2.82 | $846 | |
| Ultra | 600,000 – 999,999 | 450 / min | 375 | $2.67 | $1,600 | |
| Strategic Partner | ≥ 1,000,000 | 550 / min | 400 | $2.50 | $2,500 |
Reading your own tier at runtime
This page lists every tier that exists. To know which one you're in right now, call the Tier endpoint with your API key — it returns your current tier, the next one up, and the credits you need to bridge the gap:
The full contract, response shape, and a self-tuning rate-limiter recipe live in Account & Credits.
Failed requests are free
Credits are deducted on successful calls only. Validation failures, auth failures, rate-limit responses, and infrastructure errors all return zero-cost — the credit meter is tied to a successful, billable response, not to the request itself.
Need more than 550/min?
Above The Strategic Partner tire is custom both the rate limit and the credit pricing are negotiated. If your workload peaks above 550 requests per minute or you need predictable monthly billing instead of consumption, contact [email protected] with your peak QPS, average daily call volume, and target latency.
Designing for throughput
- Drive your limiter from the tier endpoint. Read
limit_per_minutefrom/api/panel/credits/tier/k/at startup and on a 1–5 minute interval. See Account & Credits for a full self-tuning recipe. - Stay just under the limit. Target ~90% of
limit_per_minuteto absorb clock skew across horizontally-scaled instances. - Cache aggressively. Renidly's graph changes slowly. A 24-hour TTL on enrichment results cuts both cost and traffic. See Data Freshness.
- Watch
next_tier.credits_needed. Surface it in monitoring so you know how close you are to a higher limit and can fire low-balance alerts before jobs fail. - Refresh on a rate-limit hit. If you do hit one, re-read the tier endpoint — your tier likely dropped — then back off and resume at the new limit.
- Use cursor pagination. Fetch the next page only after the current one is processed. See Pagination.