Service plans
Ankr provides the top-performing globally-distributed decentralized infrastructure of nodes to empower your Web3 projects with blockchain interaction capabilities.
Our solutions work under the following Service Plans:
- Public — public endpoints for free blockchain interaction provided with Public features and rate limits.
- Premium — private endpoints for high-performing blockchain interaction provided with Premium features and rate limits.
- Enterprise — customer-tailored solutions for the most demanding blockchain interaction cases.

Here is the list of solutions we have at your disposal on the RPC Service (opens in a new tab) platform under the Service Plan you've selected:
-
RPC/REST API — the endpoints that enable your Web3 projects to start interacting with an extensive list of supported blockchains, give access to viewing the usage statistics for the data queried, and provide the means for RPC API methods testing.
-
Advanced API — a ready-to-use indexed collection of endpoints that supports simultaneous querying of multiple blockchains (9 currently available) for the most popular Web3 scenarios at near-instant speeds; available via JavaScript/Python SDKs and React Hooks. Advanced API also gives you access to the usage statistics for the data queried.
Here is the list of blockchains supported: Chains Quickstart.
Service plans comparison
Advanced API is available for an authenticated user only.
The RPC/REST API
and Advanced API
solutions come with both Public and Premium service plans but differ significantly by the rate limits and other performance features supported depending on the plan selected.
Feature list
Feature | Public | Premium |
---|---|---|
Full and Archive data | ✅ | ✅ |
Global node coverage | ✅ | ✅ |
RPC/REST API | ✅ | ✅ |
Advanced API | ✅ (required: sign in) | ✅ |
Dashboard | ❌ | ✅ |
Usage stats and reports | ❌ | ✅ |
Private endpoints | ❌ | ✅ |
Support Polkadot, Kusama, & HECO | ❌ | ✅ |
Batch requests | ✅ | ✅ |
eth_getLogs batch size | 10 per batch | up to 1000 per batch |
Priority order | Limited during high traffic | Prioritized during high traffic |
Connection | HTTPS | HTTPS and WebSocket |
Support | Discord and Support Portal | Direct Email Support |
Terms | No Contract | Both Contract and No Contract |
Cost | Free | Pay-as-you-go |
Rate limits
Service | Public | Premium |
---|---|---|
RPC/REST API (EVM-compatible chains) | Requests across all endpoints:≈1800 requests/minute — guaranteed;>1800 requests/minute — possible(depends on the load) | Requests per endpoint: Up to ≈1.5k requests/second |
RPC/REST API (Solana) | Requests across all endpoints:≈1800 requests/minute — guaranteed;>1800 requests/minute — possible(depends on the load) | Requests per endpoint: Up to ≈4k requests/second |
Advanced API | 50 requests/minute | 1k+ requests/minute |
Charging models
Our Premium service plan users can choose to query blockchains under the following charging models:
- Pay-as-you-go — pay for each request you make.
- Subscription — pay for one-month service bundle.
Pay-as-you-go
Pay-as-you-go (PAYG) is a usage-based charging model for the Premium Plan services. PAYG means that you commit to no subscriptions but pay for each request you make. To start using the Premium Plan features, you deposit a minimum amount of 1000 ANKR tokens and create an Ankr Premium account.
Subscription
Subscription is a charging model under which you pay a fixed price for a particular bundle of services on a monthly basis. Our current 500 USD
subscription offers the following service bundle:
30M
requests per month- EVM-compatible methods for all chains (except for Solana and Advanced API)
- Team management
PAYG pricing
The price of our API Credits is pegged to USD. It means that upon using ANKR tokens for PAYG, ANKR
calculates into API Credits
at the latest ANKR/USD exchange rate.
Our PAYG pricing model: 0.10 USD = 1M API Credits

How we charge?
Premium Plan's chain requests measure in API Credits. PAYG model charges per method used in request. Various methods have different credit values per request. A method's credit value calculates based on a method's usage intensity and multiple factors that include using the computational, memory, storage, and network resources.
We charge no matter whether a request has been successful or not. In other words, a charge is taken for each request coming to our worker, regardless of a node's response.
PAYG charging summary:
Correct call
—Incorrect call
—Currect call + incorrect method
- Correct call (charged) — a request uses a supported method and has a valid JSON-RPC structure.
- Incorrect call (not charged) — a request has an invalid JSON-RPC structure or a batch request has the same ID in multiple requests. We can't parse such a request.
- Correct call + incorrect method (charged default amount) — a request uses an unsupported method though has a valid JSON-RPC structure. We charge default amount of credits for the infrastructure usage.
Pricing per request
API Type | Method | API Credits | in USD |
---|---|---|---|
Ethereum | all methods | 200 | $0.00002 |
EVM compatible | all methods | 200 | $0.00002 |
Solana | all methods | 500 | $0.00005 |
Advanced API | all methods | 700 | $0.00007 |
Other | 100 | $0.00001 |