> ## Documentation Index
> Fetch the complete documentation index at: https://docs.graphify.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The PyPI package is graphifyy, with two y's. The command is graphify.
> /graphify . is typed in an assistant chat, not in a shell.
> Use only commands, flags, and endpoints shown on these pages. Do not invent one.
> Choose the surface before you open a page. Local (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> The official site is https://graphify.com. These docs are https://docs.graphify.com.
> The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server.
> Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough.

# Rate limits and plan limits

> Per-minute request limits for Ask, query, and MCP, memory limits, plan allowances, and how to handle a 429 from Graphify.

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.

> [!NOTE]
>
> 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](https://docs.graphify.com/platform/support/pricing.md#enterprise) if you need more.

| Operation | Limit |
| - | - |
| Ask requests | 30/minute |
| Query requests | 120/minute |
| MCP requests | 240/minute |

## Memory limits

| Operation | Limit |
| - | - |
| Memory ingestion | 2,000 ingests/day |
| Stored memory | 10,000 turns/repository |
| Memory consolidation | 1 concurrent job/workspace |

## Plan allowances

Builds, reviews, and verification runs are counted per repository or per workspace, depending on the allowance. [Plans and pricing](https://docs.graphify.com/platform/support/pricing.md#hosted-plan-allowances) 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

```json 429 Too Many Requests theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
{
  "error": {
    "code": "rate_limited",
    "message": "Too many requests. Please slow down."
  },
  "meta": {
    "correlationId": "…"
  }
}
```

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

| Status and code | Meaning | What to do |
| - | - | - |
| `429` `rate_limited` | Too many requests in a short time. | Back off and retry, as above. |
| `402` `subscription_required` | The feature needs a paid plan. | Check **Billing** in the console. |
| `409` `seat_limit_reached` | Every Teams seat is assigned. | Buy more seats in **Billing**, or remove a member. |

The console shows plan limits as messages:

| Message | What it means |
| - | - |
| **Monthly indexing allowance used** | The workspace used this month's indexing allowance. It resets at the start of next month. |
| **Daily build limit reached** | The repository used today's automatic builds. It resets at 00:00 UTC. |
| **Repository too large for this plan** | The newest version was not published. The last published version still works. |
| **Monthly reviews used** | The plan's reviews for this month are used. |

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](https://docs.graphify.com/platform/support/pricing.md). For higher request limits, on Teams or Enterprise, or for your own deployment, [contact us](https://docs.graphify.com/platform/support/pricing.md#enterprise).

[PreviousPlans and pricing](https://docs.graphify.com/platform/support/pricing.md)
[NextSecurity and data handling](https://docs.graphify.com/platform/support/security.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.