Limits and Method Availability
Understand the creation limits, method restrictions, and plan-based capabilities of Tatum’s RPC Gateway, including block-range limits, item caps, and validation rules.
Gateway & Endpoint Creation Limits
To prevent abusive usage and ensure platform stability, Tatum enforces fixed limits on the number of Custom Gateways and Endpoints that can be created. Once a limit is reached, no additional items can be added until an existing one is removed.
Paid / Business Plans
- Custom Gateways: Up to 5 Once the limit is reached, an existing Gateway must be deleted to create a new one.
- Endpoints: Up to 15 After reaching the limit, a slot must be freed before adding another endpoint.
Free Plan
- Custom Gateways: 1 allowed
- Endpoints: 3 allowed
Method Range and Item Limits
Some methods available through Tatum’s Gateway include built-in request or block-range limits to ensure fair usage and consistent performance across all plans.
Additionally, certain resource-intensive methods are only available to paid customers due to their higher computational impact and infrastructure requirements.
Solana
| Method | Anonymous | Free | PayGo | Business |
|---|---|---|---|---|
getBalance | ❌ Not available | ❌ Not available | ✅ Available | ✅ Available |
getProgramAccounts | ❌ Not available | ❌ Not available | ✅ Available | ✅ Available |
getTokenAccountsByOwner | ❌ Not available | ❌ Not available | ✅ Available | ✅ Available |
Tron
| Method | Anonymous | Free | PayGo | Business |
|---|---|---|---|---|
getBlockByLimitNext | ❌ Not available | ❌ Not available | ✅ Available | ✅ Available |
EVM - eth_getLogs
The eth_getLogs method allows querying logs over a specified block range. The method enforces a maximum range size based on your plan:
| Plan | Maximum Block Range / Items |
|---|---|
| Anonymous | 100 |
| Free | 10,000 |
| PayGo | 10,000 |
| Business | 10,000 |
Note
- Keep your fromBlock → toBlock range within the allowed limit to avoid request failures.
- Large block-range queries may result in timeouts, depending on the blockchain
EVM - eth_callMany
The eth_callMany method lets you batch multiple eth_call requests into a single call. A maximum of 500 items is allowed per request.
| Plan | Availability | Max Items |
|---|---|---|
| Anonymous | ❌ Not available | – |
| Free | ❌ Not available | – |
| PayGo | ✅ Available | 500 |
| Business | ✅ Available | 500 |
How Limits Are Enforced
Each request is validated at the Gateway layer before execution.
If a request exceeds the defined thresholds or violates plan-level permissions, Tatum returns an error response.
| Error Code | Meaning | Typical Cause |
|---|---|---|
-16401 | Invalid Request | Method restricted by plan (e.g., eth_callMany on Free plan) |
-16412 | Validation Failed | Exceeded permitted range or item count (e.g., eth_getLogs) |
Recommended Practices
- Use filters and narrow block ranges when calling
eth_getLogs. - Cache responses when polling the same ranges repeatedly.
- For batching large read calls, split your arrays into smaller chunks of ≤500 items.
- Upgrade to PayGo or Business for full access to all RPC batching capabilities.
Important Notice
Gateway limits, available methods, and plan-based access rules may evolve over time.
To ensure platform stability and fair usage, Tatum continuously monitors infrastructure performance and customer usage patterns and may adjust:
- Maximum range or item limits per method
- Method availability per plan
- Error code handling or validation logic
These measures help maintain optimal performance, reliability, and fairness for all users.
Updated about 5 hours ago