BlockVectra as a QuickNode Alternative: RPC Without a Monthly Subscription

Use BlockVectra for supported occasional RPC reads without a monthly RPC subscription; authenticated access uses eligible free credits or usage billing, with a $0.01 minimum top-up excluding network gas.

Use BlockVectra for supported occasional RPC reads without a monthly RPC subscription; authenticated access uses eligible free credits or usage billing, with a $0.01 minimum top-up excluding network gas.

Comparison

Competitor figures as of 2026-10-08. BlockVectra method weights, free-plan and key limits come from GET /v1/plans and log ranges from GET /v1/chains; current figures are rendered by the components below.

MetricQuickNodeBlockVectraSources
Standard paid RPC subscriptionBuild: $49/month, monthly billing; 80M API credits includedUsage billing without a monthly RPC subscriptionPricing, plans, chains
Free-access durationOne-month trial; 10M API credits; no overageSign-up credits and eligible cycle refills; current budget belowPricing, trial rules, plans, chains

Build overage is $0.62 per million additional API credits after the included 80M, not a price for a million RPC calls. Apply the exact chain and method credit weights before estimating usage. The table uses monthly billing, excluding annual discounts and promotions; the free-access row compares duration, not the number of calls.

Why choose BlockVectra

Method prices and free-account budget

Method weights, USD conversion and the free-account budget below come from GET /v1/plans. Chain limits come from GET /v1/chains. Compare the same chain, method, block and complete result; splitting and retries change the number of calls.

Active Conversion Parameters

1 USD = 10,000 billing units, 1 billing unit = 1,000 CU (1 USD = 10,000,000 CU).

Formula: CU weight × 1,000,000 ÷ (10,000 × 1,000) USD.

MethodCU per callPrice per 1M calls (USD)
eth_blockNumber1$0.10
eth_call15$1.50
eth_getLogs30$3.00
debug_traceTransaction100$10.00
data.block5$0.50

Self-service Push supports up to 1,000,000 addresses per subscription. For 10,000,000 / 100,000,000 addresses per subscription, contact us to enable capacity.

BlockVectra task costs and request rates Free new-key default budget: 100 CU/s.

MethodExample callsCU per callTask cost (USD)Requests/s from key CU budget
eth_call1,000,00015$1.506
eth_getLogs100,00030$0.303

Task costs are list prices before free credits, gas and additional services. Request rates equal key_defaults.cu_per_sec ÷ method CU and assume only that method uses the key. Free-account caps and other traffic can reduce the usable rate; these figures are budget conversions, not measured throughput.

Current weights, prices and key limits: GET /v1/plans.

The Free Plan requires registering an account and using an API key; all keys under an account share an average of 25 calls per second (short bursts allowed). At the end of each 30-day cycle, balances below 30,000,000 CU are refilled to 30,000,000 CU.

MethodCU WeightApprox Calls / CycleApprox / DayList Price / 1M Calls
eth_blockNumber130,000,0001,000,000$0.10
eth_getBlockByNumber56,000,000200,000$0.50
eth_getBalance103,000,000100,000$1.00
eth_call152,000,00066,666$1.50
eth_getLogs301,000,00033,333$3.00
debug_traceTransaction100300,00010,000$10.00
data.block56,000,000200,000$0.50
data.address_balances251,200,00040,000$2.50
data.dex_prices152,000,00066,666$1.50
data.transaction_trace200150,0005,000$20.00

Free-account cap: up to 25 calls per second, shared across all keys in the account, all chains, and the Data API. Per-key key_defaults.cu_per_sec and burst_cu also apply. Eligible cycle refills top the free balance up to the target rather than adding a full grant. The first paid top-up stops cycle refills while preserving remaining free CU. See free plan rules.

Usage billing for intermittent workloads

For a hypothetical occasional job of 10,000 supported eth_call reads, multiply the call count by the current eth_call CU weight in the method table. Divide that usage by pricing.units_per_usd × pricing.cu_per_unit for its list-price compute cost, then deduct available free CU before calculating paid compute. Include any billable retries.

There is no monthly RPC subscription. When your balance covers the job, no additional compute funding is needed. Otherwise, check the current minimum in top-up status and follow the top-up flow; network gas is separate. Eligible unpaid accounts receive cycle balance refills; the first paid top-up stops those refills while preserving unused free CU. Rates and refill rules: plans, checked 2026-10-09, and free plan rules.

Keyless trials and programmatic Agent funding

Try a listed public.methods method at the chain catalog's public.url before creating a key. For authenticated access, programmatic sign-up lets an Agent create an account and key with a wallet signature. Agent top-ups fund the same usage balance with stablecoins; read networks, tokens and minimums from top-up status. Developers and AI Agents use the same prices and limits.

Multi-chain address Push

Watch the same address set across several supported chains in one subscription, with one HTTPS receiver. This suits wallet activity and payment notifications without maintaining a socket per chain. See self-service and enterprise address capacity; contact us to enable enterprise capacity. Address-day and delivered-event charges are separate from RPC calls and are listed in Push pricing.

RPC on Robinhood Chain and HyperEVM is listed in the chain catalog. Check methods and Push support per network; use the chain-specific starter guide and HyperEVM backfill guide for the relevant workflow.

Migration steps

  1. Inventory and coverage: list chains, methods, fixed blocks, log spans and subscription dependencies. Check methods.allow, methods.deny, public.methods, state_window_blocks and ws in the catalog. A null history window is unspecified, not archive coverage. A keyless public.url smoke test validates only its listed public methods.
  2. Key and authentication: obtain a BlockVectra key through the console or programmatic sign-up. Keep it in your server environment. RPC accepts POST /v1/{chain}/{api_key} or POST /v1/{chain} with x-api-key; Data API uses x-api-key. This Ethereum WETH decimals() example uses the header:
if [ -z "$BLOCKVECTRA_API_KEY" ]; then
  echo "Set BLOCKVECTRA_API_KEY in your server environment"
  exit 1
fi

curl --fail-with-body -sS --max-time 15 https://api.blockvectra.com/v1/eth_mainnet \
  -H 'Content-Type: application/json' \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2","data":"0x313ce567"},"latest"]}'
  1. Replay before switching: replace latest with the same supported fixed block on both providers and record the block hash. Compare returned values and JSON-RPC error, even after HTTP 200. Test representative log queries, bounded retries, rate-limit recovery and cursor resume. Migrate proprietary APIs and subscriptions separately; move traffic after the required results match.

FAQ

Does a lower method price mean a lower total task cost?

Calculate max(0, sum(calls × method CU) − available_free_cu) / (pricing.units_per_usd × pricing.cu_per_unit). Include splitting, retries and any services your task uses. Existing included credits change incremental costs; compare the complete result rather than billing-unit names.

Can I migrate by changing the endpoint?

For supported standard RPC methods, update the endpoint and path key or x-api-key header, then replay fixed-block requests. Check historical state and method coverage first. Proprietary APIs, WebSocket subscriptions and Push receivers need their own migration tests; see historical state and Webhook versus WebSocket.

Use How to choose an RPC provider for a workload checklist and self-tests.

Last updated:

On this page