A bill you can compute in advance.

Every method has a published request-unit weight, every plan a flat price. Pay by card or crypto, cancel anytime.

On-demand No plan needed
$25 per 15M request units
No monthly fee. Add a card in the dashboard, set a spending limit (new accounts start at $50, which covers 30M request units), and pay only for the blocks you start.
  • Pay only for what you use
  • A spending limit you set
  • 100 requests per second
  • Same methods as Builder
  • Email support
Start free trial
Builder
$49$41/mo
30M request units
  • All 35+ chains, one key
  • HTTPS + WebSocket
  • Email support
Start free trial
Business
$699$583/mo
500M request units
  • Everything in Pro
  • Heavy debug methods on request
  • Dedicated support
Start free trial
Enterprise
$1,499$1,249/mo
1B request units
  • Everything in Business
  • SLA & dedicated support
  • Custom chain onboarding
Start free trial
Custom
Custom
Custom volume
  • Custom volume and rate
  • SLA
  • Dedicated support, invoicing
Talk to sales

Free 14-day trial with 5M request units at 100 req/s, no credit card · yearly prices shown per month, billed annually

Compare plans in detail.

On-demandBuilderProBusinessEnterpriseCustom
Usage & limits
Monthly request unitsPay per use30M150M500M1BCustom
Request rate limit100 req/sNoneNoneNoneNoneNone
Supported networksAll 35+All 35+All 35+All 35+All 35+All 35+
Connectivity & access
HTTPS RPC
WebSocket RPC
Native gRPC (Sui, Tron)
Archive data (per chain, see Networks)
Trace & debug methods (per chain, see Networks)
Unbounded debug methods (accountRange, storageRangeAt, dumpBlock)NoNoNoOn requestOn requestOn request
Key security
IP & origin allowlists per key
Method allow/deny policies
Per-key rate limits & daily caps
Key rotation with grace period
Usage & cost control
Usage analytics & request logs
Log & usage export (CSV/NDJSON)
Usage alerts & custom thresholdSpend alerts
On-demand overage, capped by youAlwaysCustom
Teams
Team members & invites
Per-member chains, caps & permissions
Infrastructure
Automatic failover
Dedicated nodesNoNoNoNoOn requestOn request
Custom chain onboardingNoNoNoNo
Support & SLA
Support levelEmailEmailPriorityDedicatedDedicated supportDedicated support
Uptime SLANoNoNoNoUp to 99.9%Custom
Billing
Payment methodsCardCard / CryptoCard / CryptoCard / CryptoCard / CryptoCard / Crypto / Invoice
Invoicing

What would your traffic cost?

Pick a method and a monthly volume. The math is the same math billing uses, per started on-demand block.

Read-only call (no state change)

ESTIMATED MONTHLY USE
3M RU

1M calls × 3 RU = 3M RU per month

Share of Pro (150M RU)2%
Within the plancovered by $199/mo
Per call at the included rate$0.000004

Fits in the monthly allotment. Nothing extra is billed.

Published method weights.

Every JSON-RPC method has a fixed request-unit weight, published before you sign up. Multiply your call volume by these weights and you have your bill. The same table prices the REST doors (Beacon, Aptos, Tron wallet API) and native gRPC: a Sui or Tron gRPC call costs what its JSON-RPC or HTTP twin costs, Sui streams bill 1 RU per 24 KB delivered.

Full weight table in the docs →
eth_chainIdStandard reads3 RU
eth_blockNumberStandard reads3 RU
eth_callStandard reads3 RU
eth_getBalanceStandard reads3 RU
eth_getLogsLog queries4 RU
eth_sendRawTransactionWrites5 RU
debug_traceTransactionTrace & debug6 RU
trace_blockTrace & debug6 RU

Pricing questions, answered.

How does BoltRPC blockchain RPC pricing work?

Fixed monthly plans priced in request units (RUs). Each RPC method is weighted by its real server cost and those weights are published up front. Standard reads cost 3 RUs, eth_getLogs costs 4 RUs, writes cost 5 RUs, heavy methods like debug_* cost 6 RUs. You pick a plan by your monthly RU volume, starting at $49/mo for 30M RUs. No compute-unit multipliers, no hidden tiers, no surprise overage at 2 a.m. Or skip the plan: on-demand usage is $25 per 15M request units with no monthly fee, up to a spending limit you set.

What exactly is a request unit?

A request unit is the measure of one RPC call’s server cost. Because eth_blockNumber and debug_traceTransaction are wildly different workloads, a flat "one call = one request" model would either overcharge the cheap calls or undercharge the expensive ones. RUs make the billing honest: cheap methods stay cheap, expensive ones cost a little more. Every weight is published so you can calculate your monthly spend before you ship.

Are there rate limits or per-second caps?

No rate limit on monthly plans. The free trial and on-demand usage without a plan are limited to 100 requests per second (burst 200). On a monthly plan you pay for monthly request units, not for artificial burst caps: if your traffic spikes, requests still go through at full speed until you reach your monthly RU allocation. Every method’s RU weight is published up front.

What happens if I go over my monthly RU allocation?

You decide. By default nothing is billed beyond your plan. If you enable on-demand usage, extra capacity is added in fixed blocks of 15M RUs at $25 per block, and only up to a monthly spending limit you set yourself. You get email alerts at 80, 90 and 100 percent of your included units, so the bill is never a surprise. Your spending limit pays for whole blocks ($50 covers 30M request units); you get alerts at 80, 90 and 100% of it, and once it is used up, requests get HTTP 429 until you raise it. If you are consistently overshooting, that is usually a signal to move up a tier, and switching is prorated.

What about archive, trace or debug methods?

Archive depth and trace_* / debug_* support are properties of each chain’s node pool, not of your plan: the Networks page shows per chain whether the pool holds full or partial archive state and which debug and trace methods its nodes answer, and every plan gets what the chain offers at the published weights (6 RU for traces). The only plan-gated calls are the three unbounded state-iteration methods, debug_accountRange, debug_storageRangeAt and debug_dumpBlock, which are enabled per account on request from Business upward.

How is gRPC priced?

Native gRPC (Sui sui.rpc.v2 in Beta, Tron protocol.Wallet) is included on every plan at the same endpoint. A unary gRPC call costs exactly the request units of the matching JSON-RPC or HTTP method, so there is no gRPC surcharge. A Sui BatchGetTransactions or BatchGetObjects call bills once, whatever the item count. Sui server streams (Subscribe*, List*) bill by delivered data at 1 RU per 24 KB, rounded up once when the stream closes; opening a stream is free and you get five concurrent streams per key. Pick any sui_grpc_ or tron_grpc_ method in the calculator above to see the weight.

Can I switch plans at any time?

Yes. Upgrade or downgrade any time from the dashboard. Changes take effect immediately, billing is prorated. Annual plans are 17% cheaper than monthly, with the same no-lock-in switching.

Is there a free blockchain RPC trial?

Yes. 5M request units over 14 days at 100 requests per second (burst 200), no credit card required. You get a live API key within seconds and access to every chain. When the trial ends, add a card to keep the same key on on-demand usage, or choose a plan. If you do neither, the key deactivates and nothing is charged.

Can I pay per use without a plan?

Yes. Add a card in the dashboard and pay $25 per 15M request units, with no monthly fee, up to a spending limit you set (new accounts start at $50, and until your first paid invoice the limit can be at most $100, which covers 60M request units). On-demand usage without a plan is limited to 100 requests per second; a monthly plan removes that limit.

What payment methods do you accept?

Credit card and crypto on every monthly plan. On-demand usage without a plan is card only. Enterprise customers can arrange invoicing, wire transfers and custom billing terms.

Do you offer volume discounts?

Yes. The annual billing cycle gets you 17% off any self-serve tier, Enterprise included. Need more than the 1B request units on Enterprise? The Custom tier is a contact-sales plan: we scope a volume and a rate for your workload, with discounts that compound as the commitment grows.

How is BoltRPC’s RPC pricing different from compute-unit pricing?

Two structural differences. First, BoltRPC’s blockchain RPC pricing uses published, fixed RU weights per method (for example eth_getLogs = 4 RU, eth_call = 3 RU, eth_sendRawTransaction = 5 RU), so you can estimate your bill before you ship. Second, monthly plans carry no rate limit, so bursts during liquidations or token launches route at full speed until you hit your monthly allocation. That means predictable monthly bills and no surprise throttling at the worst moment.

Start with two free weeks.

5M request units over 14 days, an API key in under 60 seconds. No credit card, no commitment. Then pay per use or pick a plan.