Regions

EVMKit public APIs are exposed through regional hostnames.

Use the regional hosts directly when you care about latency, locality, or explicit failover behavior.

Hostname pattern

• Search API: https://search-<endpoint>.evmkit.app/
• RPC API: https://rpc-<endpoint>.evmkit.app/
• Streams API: wss://streams-<endpoint>.evmkit.app/

Supported endpoint families:

• Europe: eu1, eu2
• US: us1, us2
• Canada: ca1, ca2

Current public layout

The public deployment is currently split like this:

Family	RPC API	Streams API	Search API
Europe (OVH SBG)	rpc-eu1.evmkit.app, rpc-eu2.evmkit.app	streams-eu1.evmkit.app, streams-eu2.evmkit.app	search-eu1.evmkit.app, search-eu2.evmkit.app
US (NY)	rpc-us1.evmkit.app, rpc-us2.evmkit.app	streams-us1.evmkit.app, streams-us2.evmkit.app	search-us1.evmkit.app, search-us2.evmkit.app
Canada (OVH BHS)	rpc-ca1.evmkit.app, rpc-ca2.evmkit.app	streams-ca1.evmkit.app, streams-ca2.evmkit.app	search-ca1.evmkit.app, search-ca2.evmkit.app

Global aliases are also available:

• rpc.evmkit.app
• streams.evmkit.app
• search.evmkit.app

Prefer the regional hosts when you want predictable routing. Use the global aliases only when a single default entrypoint is enough; the global aliases currently target the EU deployment.

Examples:

• https://search-eu1.evmkit.app/
• https://rpc-eu2.evmkit.app/
• wss://streams-eu2.evmkit.app/pending-txs

RPC client guidance

• Use the regional RPC hosts directly when latency or explicit failover matters.
• RPC hosts require HTTPS with HTTP/2.
• POST /v1/size on the Search hosts follows the same public HTTP transport guidance as the RPC API and also requires HTTPS with HTTP/2.
• Reuse long-lived HTTP/2 connections rather than opening a new connection for each request.
• Plan for up to about 32 active HTTP/2 streams per connection.
• Keep account-level RPC connection usage conservative across all regions combined; see Rate limits for the current public guidance.

Notes

• quota and websocket connection limits remain global across regions