Tenderly

The Tenderly integration generates Node RPC Endpoints from the Tenderly public network catalog for Ethereum, Polygon, Arbitrum, Optimism, and Base.

Credential

Provide a Tenderly access key.

The key is not used to call Tenderly during discovery. It is written into each synchronized Endpoint as a path credential, appended to the generated URL when the Gateway forwards a request.

Network coverage

The integration synchronizes the EVM networks above when Tenderly advertises Node RPC for them. Use another Provider or a manual Endpoint for the rest of the Gateway catalog.

Synchronization behavior

Discovery reads the Tenderly public network catalog and keeps the entries that expose Node RPC, matching them to the Gateway catalog by EVM chain ID. Generated Endpoint URLs use the form https://<network-slug>.gateway.tenderly.co, with the access key applied as a path credential.

Synchronization publishes inventory from the current Tenderly catalog. Existing inventory remains unchanged until a complete catalog result is available.

Verification checklist

• Enable Node RPC for the required networks in Tenderly and include them in the Provider selection.
• Use another Provider or a manual Endpoint for BNB Smart Chain and non-EVM networks.
• Confirm the access key’s network permissions, then run each synchronized Endpoint health check.

See the Tenderly RPC integration overview for how synchronized Endpoints are used in Routes. Return to the Providers overview for the shared synchronization workflow and Endpoint lifecycle.