Quietforge

Note · 2026-09-21

How many developer APIs actually publish their rate limits?

In a verified sample of 60 developer APIs across 14 categories (checked 2026-09-20 against each provider's own pricing page), 31 — just over half — state no numeric rate limit on that page at all. If a rate limit matters to your integration, don't assume the pricing page has it; check the docs or account dashboard separately.

Short answer: about half. In a verified sample of 60 public developer APIs spanning 14 categories (LLM/AI, Maps/Geo, Search, Storage, Email, Payments, Weather, and more), checked against each provider's own official pricing page on 2026-09-20, 31 of 60 (52%) state no numeric rate limit on the pricing page itself — not "unlimited," just absent. If you're budgeting for an integration and rate limits matter to your architecture (retry logic, queueing, concurrency), don't assume the pricing page has the number you need.

Where the gap shows up most

Rate limits are most often missing from the pricing page (as opposed to a separate docs/dashboard page) in categories where usage is billed per-token or per-request rather than per-seat:

Why this happens

Providers billing purely on usage volume have less incentive to advertise a hard rate ceiling on the page meant to sell the plan — a visible cap reads as a limitation, not a feature. Providers selling fixed subscription tiers (SMS, some payments, some auth APIs) are more likely to list a rate limit up front because it's part of what differentiates the tiers.

What to check instead

If a provider's pricing page doesn't state a rate limit, that's not confirmation of "no limit" — check (in order): the API reference/docs page for that endpoint, the account dashboard after signing up for a free tier, or the provider's status/changelog page for throttling policy. Our API Pricing and Rate Limit Dataset tracks exactly which of these 60 APIs publish a rate limit on the pricing page and which don't, with the source URL for every row, refreshed monthly.