Rate limiting throttles requests per API key — 100 per day on free tier, 10,000 per day on pro tier — resetting at midnight UTC and returning HTTP 429 on exceed.
Last verified: April 2026
What is Rate Limiting?
Rate limiting throttles requests per API key — 100 per day on free tier, 10,000 per day on pro tier — resetting at midnight UTC and returning HTTP 429 on exceed.
Limits are enforced in Redis with a rolling counter keyed by API-key hash. When the counter trips, the gateway returns 429 Too Many Requests with a Retry-After header pointing at the next reset. Metered billing is deliberately separate: you can be within your rate limit and still hit a token budget cap or a spend ceiling.
FAQ
Rate Limiting FAQ.
Common questions about Rate Limiting in the AGNT platform.
Rate limiting throttles requests per API key — 100 per day on free tier, 10,000 per day on pro tier — resetting at midnight UTC and returning HTTP 429 on exceed.
People also ask.
Related terms
API Key
An AGNT API key is a credential of the form agnt_live_[32-char-hash], stored as SHA-256 inside AGNT, used to authenticate every Open Network request against a tier and a daily quota.
Token Budget
A token budget is the daily LLM token ceiling per tier — 50,000 for free, 200,000 for starter, 1,000,000 for pro — tracked in Redis with a 24-hour expiry to cap runaway spend.
Metered Billing
Metered billing is AGNT's per-use pricing model for API consumers — each booking.confirm call costs $0.25, batched nightly to Stripe as usage records with no upfront fees.
Source: agnt-backend/app/core/limiter.py
Share as social post
What is Rate Limiting? Rate limiting throttles requests per API key — 100 per day on free tier, 10,000 per day on pro tier — resetting at midnight UTC and returning HTTP 429 on exceed. https://agntdot.com/glossary/rate-limiting
228 / 280 chars
See it in action.
Now you know what Rate Limiting means. Try the live scan demo or read the developer docs to go deeper.