Hypertune Rate Limits
Hypertune does not publish numeric per-request rate limits for the Edge GraphQL API or SDK initialization. Instead, plan capacity is governed by metered quotas: included CDN requests (SDK initialization / GraphQL Edge evaluation) and analytics events per month, with per-million overage billing on paid tiers. Because SDKs fetch flag logic once and then evaluate flags locally in memory, the dominant request volume is initialization and background log flushing rather than per-flag-evaluation calls.
Hypertune Rate Limits is the machine-readable rate-limit profile for Hypertune on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests and events.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Feature Flags, Experimentation, Analytics, Edge, and Rate Limiting.
Limits
Policies
Sources
- https://www.hypertune.com/pricing
- https://docs.hypertune.com/pricing/overview
- https://docs.hypertune.com/concepts/architecture
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/hypertune-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.