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, in the API Commons Rate Limits shape.
It captures 5 rate-limit definitions, measuring requests and events.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
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.
generated, dated 2026-06-20.
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.