Overview
Overview of EVMKit and reference documentation for Pipelines, Pipelines API, RPC API, Streams API, authentication, CU billing, and rate limits.
EVMKit is an API platform for latency-sensitive EVM workflows.
What it is for
Section titled “What it is for”- individuals that need more than standard RPC access
- automation and delivery systems
- workflows that depend on deterministic simulation, lightweight state reads, managed event filtering, and realtime pending-state updates
Rather than exposing only generic node access, EVMKit combines public RPC methods, live websocket streams, and managed pipelines for filtering matched on-chain activity and delivering it to configured webhook destinations. Pipelines can be configured directly in the account dashboard UI or managed actively through Pipelines API with the same account API key.
Operating model
Section titled “Operating model”EVMKit remains infrastructure-only.
It does not:
- store or handle keys
- custody funds
- initiate, sign, broadcast, or relay on-chain transactions
What EVMKit returns
Section titled “What EVMKit returns”Instead, it returns deterministic, inspectable outputs your systems can consume directly:
- matched event deliveries to configured destinations
- delivery logs and retry state for managed pipelines configured from the dashboard or the management API
- stateless simulation and tracing results
- lightweight state reads
- pending state changes over websocket
Products
Section titled “Products”EVMKit has one managed product and two public technical APIs:
- Pipelines for managed event delivery through the account dashboard UI
- RPC API on regional hosts like
https://rpc-<endpoint>.evmkit.app/ - Streams API on regional hosts like
wss://streams-<endpoint>.evmkit.app/
Management API
Section titled “Management API”- Pipelines API for programmatic source, destination, route, overview, and delivery management using your account
X-Api-Key
Pricing model
Section titled “Pricing model”Public subscriptions combine:
- one or more API access fees
- one daily CU tier
- monthly or quarterly billing
Burst limits, websocket capacity, managed pipeline capacity, and priority support are then derived from that selection.
Related pages
Section titled “Related pages”- Authentication for
X-Api-Keyusage across RPC API, Streams API, and Pipelines API - Regions for regional hostname patterns
- Billing & CU pricing for plan allowances and per-endpoint CU pricing
- Rate limits for shared
12sCU limits and websocket caps - Performance for multi-account RPC benchmark snapshots