Skip to main content
Graphify limits how fast you can call Ask, query, and the hosted MCP server, and how much each plan can build, review, and verify. A request over a rate limit returns HTTP 429 with the code rate_limited. Wait a few seconds and retry.
This page covers Graphify, the hosted product. Graphify Local, the open-source CLI, has no rate limits; it runs on your machine.

​
Request rate limits

These are the default limits on every plan. They may change as we tune the service. Teams and Enterprise workspaces can get higher limits; contact us if you need more.

​
Memory limits

​
Plan allowances

Builds, reviews, and verification runs are counted per repository or per workspace, depending on the allowance. Plans and pricing has the full table for each plan. All hosted plans allow 1 index build at a time per repository and 10 across a workspace.

​
What a 429 looks like

429 Too Many Requests
The response has no Retry-After header. Back off and retry:
  1. Wait 2 seconds, then retry the same request.
  2. If it fails again, double the wait each time, up to about 60 seconds.
  3. Add a little random jitter, so parallel agents do not retry in step.
The usual cause is an agent calling query_graph or Ask in a tight loop. Tell the agent to reuse the answers it already has.

​
Other limit responses

The console shows plan limits as messages: Include the correlationId from the response, or the X-Correlation-ID header, when you contact support. It lets the team find your request.

​
Need more capacity

Pro and Teams raise build, review, and verification allowances; see Plans and pricing. For higher request limits, on Teams or Enterprise, or for your own deployment, contact us.