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

# Rate Limits

> Request limits for the Conduit API and MCP server.

Conduit rate-limits API and MCP usage to keep workspace data access predictable for every customer.

## Default Limit

By default, Conduit allows **120 requests per minute per workspace** across REST API requests and workspace-scoped MCP tool calls.

Some workspaces may have higher limits based on plan or entitlement. Contact [support@conduit.ai](mailto:support@conduit.ai) if your integration needs sustained higher throughput.

## Shared API and MCP Budget

REST API requests and MCP tool calls share the same workspace-level rate limit. For example, calls to `GET /v1/reservations` and MCP tools that read reservations count toward the same workspace budget.

Requests that do not target a workspace yet, such as listing accessible workspaces or MCP initialization, are limited separately per token at the same default rate.

## Handling 429 Responses

When a request exceeds the limit, Conduit returns `429 Too Many Requests` and includes a `Retry-After` header with the number of seconds to wait before retrying.

Use exponential backoff with jitter for automated retries, and avoid retrying write requests unless you provide an idempotency key.