Qodo · Rate Limits

Qodo Rate Limits

Qodo does not publish per-endpoint HTTP rate limits because it has no documented public REST API. Usage is governed by subscription-tier allowances instead: the free Developer tier caps monthly PR reviews and IDE/CLI credits (organization-wide), while Teams and Enterprise raise or remove those caps per active seat. Self-hosted PR-Agent (Apache-2.0) is not rate-limited by Qodo; its throughput is bounded by the user's own LLM provider rate limits and infrastructure.

Qodo Rate Limits is the machine-readable rate-limit profile for Qodo on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring reviews, credits, seats, and requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Code Review, Code Integrity, Developer Tools, and Pull Requests.

4 Limits Throttle: 429
AICode ReviewCode IntegrityDeveloper ToolsPull RequestsRate LimitingQuotas

Limits

Free PR Reviews organization
reviews
30 per month (Developer tier)
Organization-wide allowance on the free tier; raised on Teams/Enterprise.
Free IDE / CLI Credits organization
credits
250 per month (Developer tier)
Organization-wide allowance on the free tier; raised on Teams/Enterprise.
Teams / Enterprise Allowances account
seats
see provider documentation
Allowances scale per active seat; negotiated for Enterprise.
Self-Hosted PR-Agent deployment
requests
bounded by user's own LLM provider limits
Qodo imposes no rate limit on self-hosted PR-Agent; the configured LLM API governs throughput.

Policies

Tiered Allowances
Usage caps loosen from Developer (free) to Teams to Enterprise.
Active-Seat Metering
Only users who trigger reviews or use the IDE/CLI consume an allowance.
Self-Hosted Independence
Self-hosted PR-Agent throughput depends on the operator's LLM provider and infrastructure, not Qodo.

Sources