Overview
Overview of EVMKit and reference documentation for the public Search API, RPC API, Streams API, authentication, CU billing, and rate limits.
EVMKit is a public API platform for latency-sensitive EVM workflows.
What it is for
Section titled “What it is for”- teams that need more than standard RPC access
- search-driven, automation, and monitoring systems
- workflows that depend on deterministic simulation, lightweight state reads, sizing, monitoring, and realtime pending-state updates
Rather than exposing only generic node access, EVMKit combines public RPC methods with purpose-built APIs for sizing ranges, monitoring positions, and consuming pending-state streams. This gives external systems a single integration surface for state-aware workflows while keeping control in the client runtime.
Operating model
Section titled “Operating model”EVMKit remains infrastructure-only.
It does not:
- hold custody
- receive private keys
- sign transactions
- submit transactions on your behalf
What EVMKit returns
Section titled “What EVMKit returns”Instead, it returns deterministic, inspectable outputs your systems can consume directly:
- sized input ranges for a raw calldata
- monitored positions and unhealthy-position events
- stateless simulation and tracing results
- lightweight state reads
- pending state changes over websocket
Public APIs
Section titled “Public APIs”EVMKit exposes three public APIs:
- Search API on regional hosts like
https://search-<endpoint>.evmkit.app/ - RPC methods on regional hosts like
https://rpc-<endpoint>.evmkit.app/ - Streams API on regional hosts like
wss://streams-<endpoint>.evmkit.app/
Related pages
Section titled “Related pages”- Authentication for
X-Api-Keyusage - 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