Catalog fallback
The built-in network table remains available during temporary Alchemy catalog unavailability, while existing inventory is preserved.
Alchemy integration
Connect Alchemy to your RPC Gateway
Generate Endpoint inventory from the Gateway network catalog, apply your Alchemy API key as the upstream path credential, and route applications through synchronized targets.
Integration details
Synchronization starts with the built-in Gateway network table and refines it with Alchemy's public network catalog.
- Credential
- Alchemy API key
- Network scope
- Every chain-network pair in the RPC Gateway catalog
- Transport
- JSON-RPC, plus TRON native HTTP API
How Alchemy synchronization works
Path credential handling
Generated URLs use Alchemy's /v2 form, with your API key applied as the upstream path credential.
Two TRON transports
Each selected TRON network produces one JSON-RPC Endpoint and one native HTTP API Endpoint.
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 Alchemy integration guideExplore RPC failover
Next step
Use Alchemy behind your Gateway
Add your Alchemy API key, select the networks you use, and review the synchronized Endpoints before adding them to Routes.