Public discovery
The access key is not sent to Tenderly during discovery; the Gateway reads the public Node RPC catalog.
Tenderly integration
Connect Tenderly Node RPC to your Gateway
Discover Tenderly Node RPC networks, match them to the Gateway catalog by EVM chain ID, and publish synchronized Endpoints for application Routes.
Integration details
Discovery keeps Tenderly catalog entries that expose Node RPC and matches them to supported EVM networks by chain ID.
- Credential
- Tenderly access key
- Network scope
- Ethereum, Polygon, Arbitrum, Optimism, and Base
- Transport
- JSON-RPC
How Tenderly synchronization works
Generated URL form
Synchronized Endpoints use Tenderly's network-slug gateway URL and apply the access key as the upstream path credential.
Complete-result updates
Existing inventory remains unchanged until discovery returns a complete current catalog result.
Use synchronized Endpoints in Routes
Review synchronized inventory, then attach matching Endpoints to a Gateway Route manually or associate the Provider with an App. Route configuration determines priority, weights, and attempt bounds; the Gateway applies operation-aware failover internally.
Read the complete Tenderly integration guideExplore RPC failover
Next step
Use Tenderly Node RPC behind your Gateway
Add your access key, select the Node RPC networks you use, and review the synchronized Endpoints before routing traffic.