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

# Usage limits

> Plan API traffic in Remapdb and keep request volume inside safe daily limits.

Use this page to prevent limit-related interruptions in API access workflows, including direct API requests and MCP-based AI tool connections.

## Current API rate limits

* Up to **120 requests per minute**

<Info>
  Use 120 requests/minute as your planning baseline unless support confirms a different account-specific limit.
</Info>

## What this means in daily operations

* 120/minute is about 2 requests/second on average.
* Short bursts can still happen, but sustained traffic should stay under budget.
* MCP-based AI tools can make several API-backed calls while searching or drilling into vehicle data.
* Contact support if your normal traffic now exceeds your current baseline.

## Plan your request budget

<Steps>
  <Step title="Estimate your normal traffic">
    Calculate how many API calls one user journey triggers, including backend services, workers, batch jobs, and MCP clients connected through [AI Integrations](/api/ai-integrations).
  </Step>

  <Step title="Add safety headroom">
    Reserve part of the budget for retries, support checks, and traffic spikes.
  </Step>

  <Step title="Set soft alerts">
    Add internal alerts around 70%, 85%, and 95% of daily capacity.
  </Step>

  <Step title="Reduce avoidable calls">
    Cache stable responses and remove duplicate polling.
  </Step>

  <Step title="Review usage every week">
    Compare forecast vs real usage and adjust before limits become incidents.
  </Step>
</Steps>

## If you are close to today’s limit

* Pause non-critical background jobs.
* Increase cache duration for low-change data.
* Investigate duplicate or noisy request sources.
* Keep only customer-critical API calls active.
* Contact support if your normal traffic now exceeds your current baseline.

<Warning>
  Do not wait for a hard-limit event in production. Use soft alerts and early traffic controls.
</Warning>

## Related actions

* [API](/api)
* [AI Integrations](/api/ai-integrations)
* [Best practices](/api/best-practices)
* [Plan access](/api/plan-access)