Zephex applies monthly and burst controls per API key so request volume stays predictable and abuse stays contained.
| Plan | Monthly Requests | Per-minute cap | Concurrent requests |
|---|---|---|---|
| Free | 300 | 10 | 1 |
| Pro | 3,500 | 60 | 3 |
| Max | 10,000 | 200 | 10 |
Monthly allowance is not the only limit. Each plan also has a shorter burst cap and a concurrent request ceiling to prevent one key from overwhelming the hosted endpoint.
Every API response includes:
X-RateLimit-Limit: 300X-RateLimit-Remaining: 247X-RateLimit-Reset: 1714521600X-RateLimit-Reset is a Unix timestamp in seconds for when the monthly counter resets.
Limits reset on the first day of each month at 00:00 UTC. Usage is tracked per API key, not per account. If you have multiple keys, each key has its own counter that all count toward your plan's monthly total.
scope_task before code-reading sessions to reduce wasted tool calls.get_project_context once at the start of a session rather than calling it repeatedly.{ "error": "rate_limit_exceeded", "message": "Monthly limit of 300 requests reached. Upgrade to Pro for 3,500 requests.", "reset_at": "2026-05-01T00:00:00Z", "upgrade_url": "https://zephex.dev/pricing"}