Greptile · Rate Limits

Greptile Rate Limits

Greptile enforces per-account limits on its REST API. Query and search calls are metered and subject to per-account request throttling, and repository indexing is an asynchronous, queued operation bounded by repository size and account tier rather than a fixed per-minute ceiling. Specific numeric limits are not published in the public API reference and are not reconciled in this artifact; verify in the Greptile dashboard or with support.

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

It captures 4 rate-limit definitions, measuring requests and jobs.

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

Tagged areas include AI, Codebase Understanding, Code Review, Code Search, and Developer Tools.

4 Limits Throttle: 429
AICodebase UnderstandingCode ReviewCode SearchDeveloper ToolsRate LimitingQuotasThrottling

Limits

Query Requests account
requests
see provider documentation
Per-account throttling on POST /query; varies by plan and tier.
Search Requests account
requests
see provider documentation
Per-account throttling on POST /search; varies by plan and tier.
Repository Indexing account
jobs
queued / size-bounded
POST /repositories is asynchronous; throughput bounded by repo size and tier, not a fixed RPM.
Concurrent Indexing Jobs account
jobs
see provider documentation
Number of repositories that can index simultaneously depends on tier.

Policies

Tiered Limits
Limits and concurrency scale with paid and Enterprise plans.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After.
Asynchronous Indexing
Submit a repository, then poll GET /repositories/{repositoryId} until a sha is present before querying.

Sources