> For the complete documentation index, see [llms.txt](https://docs.tajirchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tajirchain.com/api-documentation/rate-limiting-and-usage-policies.md).

# Rate Limiting & Usage Policies

### **Default Limits**

Rate limits may differ based on your RPC provider or whether you are using public or private infrastructure.

* **Requests per second:** varies by provider (public RPC endpoints are more restrictive)
* **Burst capacity:** configurable for private or enterprise nodes
* **Heavy endpoints:** may apply stricter limits (e.g., block traces, logs, debug endpoints)

When a limit is exceeded, the API may return:

* **HTTP 429 — Too Many Requests**
* Optional `Retry-After` header indicating when to resume requests

***

### **Best Practices**

To avoid throttling and ensure efficient use of RPC bandwidth:

* Use caching for repeated or identical queries
* Avoid polling full blocks repeatedly — prefer filtered queries
* Use WebSocket or subscription-based APIs for real-time events
* Batch RPC requests where possible (`eth_batch`, multi-call libraries)
* Use indexing services instead of querying historical logs repeatedly

***

### **Abuse Protection**

Tajir infrastructure automatically monitors for patterns that degrade network performance.

Protections may include:

* **Automatic throttling** for sustained high-volume traffic
* **Temporary bans** for excessive or abusive queries
* **Progressive penalties** for repeated violations
* **IP-based or key-based filtering** depending on the provider

If you believe a ban was applied incorrectly, contact your RPC provider or node operator.