Set custom rate limits for model provider API calls. Control usage by request count, cost, or custom properties to manage expenses and prevent unintended overuse.
1000 requests per day
or 60 requests per minute
. By implementing rate limits, you can prevent abuse while protecting your resources from being overwhelmed by excessive traffic.
Helicone-RateLimit-Policy
header to your requests:
Helicone-RateLimit-Policy
header uses this format:
1000
for 1000 requests3600
for 1 hour, 86400
for 1 dayrequest
(default) or cents
for cost-based limiting.Example: u=cents
to limit by spending instead of request countuser
for per-user limits, or custom property name for per-property limits. Omit for global limits.Example: s=user
or s=organization
Helicone-User-Id
header. See User Metrics for more details.Helicone-RateLimit-Limit
: The quota for the number of requests allowed in the time window.Helicone-RateLimit-Policy
: The active rate limit policy.Helicone-RateLimit-Remaining
: The remaining quota in the current window.Need more help?