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

# Rate Limits

> Understanding Clado API rate limits and usage guidelines

## Endpoint-Specific Rate Limits

Each endpoint has specific rate limits based on your tier (requests per minute):

| Endpoint | Free | >\$0 paid | \$50 paid | \$250 paid |
| - | - | - | - | - |
| **Search People** | 20 | 20 | 200 | 400 |
| **Get Contact Information** | 0 | 5 | 60 | 120 |
| **Scrape LinkedIn Profile** | 15 | 15 | 150 | 300 |
| **Get LinkedIn Profile** | 20 | 20 | 200 | 400 |
| **Get Post Reactions** | 10 | 10 | 100 | 200 |
| **Initiate Deep Research** | 5 | 5 | 50 | 100 |

## Handling Rate Limits

When you exceed the rate limit, the API returns a `429 Too Many Requests` status code. The response includes:

```json theme={null}
{
  "error": "Rate limit exceeded",
  "retry_after": 60
}
```

### Best Practices

1. **Implement exponential backoff** - When receiving a 429 response, wait before retrying
2. **Monitor rate limit headers** - Track your usage to avoid hitting limits
3. **Spread requests over time** - Avoid bursts/concurrent requests
4. **Cache responses** - Store frequently accessed data locally when possible

## Custom Rate Limits

Enterprise customers can request custom rate limits tailored to their needs. Contact our [sales team](https://cal.com/team/clado/support) to discuss custom limits.

## Questions?

If you have questions about rate limits or need higher limits, please [contact support](mailto:founders@clado.ai).


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