One Access Point
Use the same public entry point for cache hits and Endpoint-backed requests.
Free RPC
Start with one API Key and 20 chain · network pairs. Documented reads check the shared cache first, while your own upstreams cover the rest.
RPC Gateway checks the shared cache for an explicit set of JSON-RPC and TRON native HTTP API request shapes. Each hit returns without an upstream call; a miss continues through the configured Route.
Use the same public entry point for cache hits and Endpoint-backed requests.
The documentation lists every supported method and parameter form.
Pair cached reads with a matching Endpoint-backed Route for additional methods and data.
Create Access Points for supported EVM networks, Solana, Bitcoin, Litecoin, and TRON. Authentication, rate limits, and Usage accounting stay consistent across the Gateway surface.
Next step
Create an App for its API Key, then choose a documented request. Add an Endpoint-backed Route when you need broader coverage.