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

# Rate Limits

> Reference for Webacy API rate limits by plan tier, including per-second and per-minute quotas, 429 handling, and best practices for staying under limits.

## Understanding Rate Limits

Rate limits define the maximum number of requests your application can make during a given period of time. If a limit is exceeded, the API will temporarily reject additional requests until your quota resets.

To build reliable integrations, we recommend:

* Batching requests where appropriate
* Using webhooks instead of polling when possible
* Caching responses that do not require real-time updates
* Implementing retries with exponential backoff

If you outgrow a tier or need higher rate limits, you can upgrade to the next tier, or get in touch with our team.

## Demo API Key Rate Limits

When you create an API Key in the [Developer Portal](https://developers.webacy.co/), it is assigned to the Demo Plan (Free).

The following are the rate limits allocated to a Demo Tier API Key:

* 2,000 [Compute Units](/compute-units) (CUs) per month
* 2 requests per second
* Burst capacity: 5 requests

The Demo Plan Rate Limits are restrictive on purpose, and will not support a production environment. You can upgrade your plan to higher tiers in the Developer Portal.

<Note>
  **Need higher limits?** Production and enterprise tiers offer significantly increased rate limits. Contact us at [info@webacy.com](mailto:info@webacy.com) to upgrade your plan.
</Note>

## Handling Rate Limits

When you exceed the rate limit, the API returns a `429 Too Many Requests` response:

```json theme={null}
{
  "message": "Rate limit exceeded"
}
```

## Best Practices

<Tip>
  Implement exponential backoff when you receive a 429 response.
</Tip>

* **Cache responses** - Avoid redundant API calls for the same data
* **Batch requests** - Use batch endpoints where available
* **Monitor usage** - Use the [API Usage](/api-reference/api-usage/get-api-usage-for-specified-dates) endpoint to track consumption
* **Implement queuing** - Queue requests during high-traffic periods

## Scaling your Integration

When your integration is production-ready and you need higher limits:

1. **Developer Portal** - Upgrade at [developers.webacy.co](https://developers.webacy.co/)
2. **Account Manager** - Contact your account manager for enterprise plans
3. **Support** - Email [info@webacy.com](mailto:info@webacy.com)

As your application grows, Webacy is designed to scale with it.

Whether you're screening thousands of wallets, monitoring large portfolios, or processing millions of blockchain events, higher request limits and enterprise usage plans are available. If your expected traffic exceeds your current allocation, contact the Webacy team to discuss a plan that fits your deployment.

## What's Next

<Card title="Compute Units (CUs)" icon="stop-circle" horizontal href="/compute-units">
  Learn how Compute Units measure the processing and intelligence required for each Webacy API request.
</Card>