Skip to main content
This page tracks the rollout of plans, quotas, and data-delivery features, and lists the actions existing API users should take. Dates are added here when each stage ships. Nothing on this page is a commitment until it has a date.

​
Rollout status

Planned means the behavior is specified in these docs so you can design against it, but calling the route today returns 404 and the headers are absent. Pilot means the feature is enabled for selected organizations and may still change; pilot participants are contacted directly.

​
Migration guide for existing API users

If you integrated before plans launched, here is what changes and what does not.

​
Nothing you rely on today breaks

  • Routes, parameters, and response bodies of the six current-data endpoints are unchanged.
  • The error envelope keeps code, message, param, and help_url. New fields are additive.
  • Your existing API keys keep working. No re-issue is required.

​
Wording change: from “per API key” to “per organization”

Earlier versions of these docs described rate limits as “per API key, per endpoint”. Limits are now defined per organization:
  • All keys in your organization share one daily quota and one burst limit.
  • Official MCP connections draw from the same pool.
  • Creating more keys does not create more capacity. If you were relying on multiple keys to multiply throughput, size your usage against a single organization pool and consider Builder.
The old per-route limits remain in place as an abuse backstop, so a request can still be rejected for exceeding a route limit even when the organization has quota left.

​
/v1/updates is unchanged, and is not a change feed

/v1/updates continues to return recently added models within a 1–30 day lookback. It does not report score, ranking, or pricing changes, and has no cursor. The incremental updates API (/v1/changes) is a separate, Builder-and-above feature. Keep using /v1/updates for “what’s new”; move to /v1/changes when you need a durable sync.

​
Effective dates and grandfathering

  • Plan enforcement launches in two steps. First, quota headers appear on responses and usage is measured only; no request is rejected for quota. Then, on an announced date, limits are enforced. Both dates will be added to this page and emailed to the address on your developer account at least 14 days in advance.
  • At enforcement, every organization without a subscription is on Community.
  • Organizations whose measured usage exceeds Community limits receive a time-limited grace period before enforcement applies to them. Grace is temporary; there is no permanent grandfathering of pre-plan usage levels.
  • Attribution requirements for public Community display apply from enforcement. Integrations that already show a source link are eligible for the verified bonus once verification launches.

​
What to do now

1

Consolidate keys to one organization

If you created keys under several accounts to spread load, pick one organization and migrate to it. Quota follows the organization.
2

Estimate your daily data responses

Count 2xx responses per UTC day. If it is regularly above 500, plan for Builder; above 5,000, contact sales.
3

Handle 429 by limit_type

Update your client to read error.limit_type and reset_at, and to stop polling when the daily quota is exhausted. See Rate limits and headers.
4

Add attribution if you display data publicly

Community users showing LLM Stats data publicly need a source link or badge. See Attribution. Doing it now earns the verified bonus as soon as verification launches.
5

Confirm your rights

If you redistribute the data — as a dataset, an API, or inside a paid product — you need a Commercial agreement regardless of volume. See Plans and quotas.

​
History

​
Plans and quotas
Documented the three-plan model, organization-level quotas and burst limits, response headers, stable error codes, historical data, bulk snapshots, incremental updates, webhooks, attribution, and embeds ahead of rollout. Corrected the previous “per API key” rate-limit wording to “per organization”. No API behavior changed.