BlockVectra as a Chainstack Alternative: Method Prices for Additional Reads

Choose BlockVectra for lower list prices on additional supported EVM reads and usage billing without a monthly RPC subscription.

Comparison

Competitor figures verified on 2026-10-08. Current BlockVectra figures are shown by the API-backed tables below.

The Developer rates are incremental overage after the included quota, not prices for every call. Full requests use 1 RU; archive-class requests use 2 RU. For Global Nodes, eligible EVM methods targeting blocks at least 127 blocks behind the tip are archive-class; for logs, inspect the billed starting block. Node mode can change the classification. Apply the current RU rules to the exact request before comparing.

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.

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.

Additional reads priced by method

For a metered plan, calculate subscription + max(0, used RU − included RU) × extra USD per million RU / 1,000,000, then compare supported reads with the current BlockVectra method table. Deduct available free CU and include the calls needed for chunking and retries.

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 'User-Agent: curl BlockVectraQA/1' \
  -H "x-api-key: $BLOCKVECTRA_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2","data":"0x313ce567"},"latest"]}'

3. 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.