Rybbit · Rate Limits

Rybbit Rate Limits

Rybbit rate-limits the API on Rybbit Cloud only, in two dimensions at once: a BURST bucket that is identical on every plan (50 requests, refilling continuously at 5 per second) and a DAILY QUOTA that scales with the plan (5,000/day on Standard, 25,000/day on Pro, resetting at 00:00 UTC). Limits apply per CREDENTIAL OWNER, never per key — creating more keys splits an existing budget rather than adding to it — and an OAuth/MCP token draws on the same budget as the user's personal keys. Requests refused by the burst limit do not count against the daily quota. Self-hosted (AGPL-3.0) instances are not rate limited at all and send no rate-limit headers.

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

It captures 5 rate-limit definitions, measuring requests.

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

Tagged areas include Analytics, Web Analytics, Product Analytics, Privacy, and Open Source.

5 Limits Throttle: 429
AnalyticsWeb AnalyticsProduct AnalyticsPrivacyOpen SourceRate LimitingQuotasThrottling

Limits

Burst — all cloud plans credential-owner
requests
50 per 10 seconds
Identical on Standard and Pro. Spend all 50 at once, then continue at 5/s. Rejections here are cheap — they clear in about a second and are not charged to the daily quota.
Daily quota — Standard credential-owner
requests
5000 per day
Daily quota — Pro credential-owner
requests
25000 per day
Free / Basic account
requests
0
API keys are not available on the Free/Basic tier.
Self-hosted instance
requests
unlimited
Neither tier applies to a self-hosted instance, and no rate-limit headers are sent.

Policies

Two-dimensional limiting
Every request is charged against both a shared burst bucket and a plan-scaled daily quota; the response reports both.
Advisory headers
Rate-limit headers are advisory — a few endpoints resolve credentials outside the standard path and omit them — so clients must still handle a 429 without having seen a warning.
Per-owner, not per-key
Minting extra keys divides an existing budget. Scale by plan, not by key count.
Backoff by scope
A burst rejection clears in about a second; a daily rejection lasts until 00:00 UTC. Read `scope` before retrying.
Self-host exemption
Open-source self-hosted deployments are not rate limited.

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/rybbit-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 email required.

GitHub Google LinkedIn

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