Current API rate limits
- Up to 120 requests per minute
Use 120 requests/minute as your planning baseline unless support confirms a different account-specific limit.
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
1
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.
2
Add safety headroom
Reserve part of the budget for retries, support checks, and traffic spikes.
3
Set soft alerts
Add internal alerts around 70%, 85%, and 95% of daily capacity.
4
Reduce avoidable calls
Cache stable responses and remove duplicate polling.
5
Review usage every week
Compare forecast vs real usage and adjust before limits become incidents.
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.