Skip to content
EVMKit Docs EVMKit Docs
Back to site
EVMKit Docs EVMKit Docs
Site

Docs Billing & CU pricing

Billing & CU pricing

Plan comparison and CU pricing for the public Search API, RPC methods, and Streams API state changes.

The public Search API, RPC API, and Streams API are metered in compute units (CUs).

Pricing now has two public tracks: multiselect core APIs with priced combinations, and higher-capacity bundles.

All offerings use the same per-request CU pricing, so moving to a different plan changes included capacity rather than per-request CU weights.

For the shared short-window limiter, see Rate limits.

SelectionPrice / monthIncluded CU / dayCU / 12s windowActive websocket connections
Streams APIEUR 8012,000,0003,0002
RPC APIEUR 10016,000,0004,0000
Search APIEUR 16020,000,0006,0000
  • core API selections can be billed monthly or quarterly
  • quarterly billing applies a 10% discount to the monthly subtotal and is invoiced for 3 months up front
  • single-API selections and multi-API combinations each have their own allowance, burst limit, and websocket cap
CombinationPrice / monthIncluded CU / dayCU / 12s windowActive websocket connections
Streams + RPCEUR 15020,000,0005,0003
Streams + SearchEUR 19024,000,0007,0003
RPC + SearchEUR 22026,000,0007,5000
All 3 APIsEUR 30030,000,0008,4003
  • combinations can be billed monthly or quarterly
  • quarterly billing applies a 10% discount to the monthly subtotal and is invoiced for 3 months up front
  • combinations include discounted pricing relative to buying each API separately
  • allowance, short-window rate limits, and websocket caps are enforced per account and shared across API keys and regions
BundlePrice / monthIncluded CU / dayCU / 12s windowActive websocket connectionsMonitoring endpoints
ProfessionalEUR 1,200180,000,00050,0005No
AdvancedEUR 2,000360,000,000100,00010Yes
  • bundles can be billed monthly or quarterly
  • quarterly billing applies a 10% discount to the monthly subtotal and is invoiced for 3 months up front
  • monitoring access includes GET /v1/monitoring/positions and GET /v1/monitoring/unhealthy/ws
  • allowance, short-window rate limits, and websocket caps are enforced per account and shared across API keys and regions

If you need more CU capacity, contact support at support@evmkit.app.

MethodPrice
evmkit_prepare1 CU per started 100k gas, minimum 1 CU
evmkit_prepareRaw1 CU per started 100k gas, minimum 1 CU
evmkit_call1 CU per started 100k gas, minimum 1 CU
evmkit_trace1 CU per started 100k gas, minimum 1 CU
evmkit_pendingBlock1 CU
MethodPrice
eth_getBlockByHash2 CU
eth_getBlockByNumber2 CU
eth_getBlockReceipts2 CU
eth_getRawTransactionByHash0.5 CU
eth_getTransactionByHash0.5 CU
eth_getRawTransactionByBlockHashAndIndex2 CU
eth_getTransactionByBlockHashAndIndex2 CU
eth_getRawTransactionByBlockNumberAndIndex2 CU
eth_getTransactionByBlockNumberAndIndex2 CU
eth_getTransactionBySenderAndNonce0.5 CU
eth_getTransactionReceipt0.5 CU
eth_getBalance0.5 CU
eth_getStorageAt0.5 CU
eth_getTransactionCount0.5 CU
eth_getCode0.5 CU
eth_gasPrice0.5 CU
eth_maxPriorityFeePerGas0.5 CU
eth_blobBaseFee0.5 CU
eth_getLogs2 CU
EndpointPrice
POST /v1/size1 CU base per sized item + 1 CU per started 100k gas per simulation
GET /v1/monitoring/positions10 CU
GET /v1/monitoring/unhealthy/ws connection100 CU
GET /v1/monitoring/unhealthy/ws published event1000 CU
Stream actionPrice
WebSocket connection10 CU
Published state change on a subscribed stream1 CU
  • billed RPC methods, billed Search API requests, billed monitoring requests, and billed Streams API actions require an active subscription and enough remaining allowance for the request reservation
  • evmkit_prepare, evmkit_prepareRaw, evmkit_call, and evmkit_trace reserve 1 CU up front and then settle to the gas-based price from the response
  • POST /v1/size is capped to 18 iterations per item
  • POST /v1/size settles to the per-item 1 CU base plus gas-priced simulations
  • profile=fast, balanced, and deep reserve the per-item base plus the max gas-priced simulation cost for 6, 10, and 18 capped iterations
  • monitoring endpoints are available only on the Advanced plan
  • short-window RPC rate limiting returns 434; see Rate limits
  • billed RPC requests return 402 Payment Required when no allowance remains
  • billed Search API sizing requests return 402 Payment Required when no allowance remains
  • billed monitoring requests return 402 Payment Required when no allowance remains or the plan is below Advanced
  • Streams API connections are rejected or closed when billed state changes cannot be covered