Providers
A Provider connects RPC Gateway to an RPC vendor account. It uses the vendor API key or secret to discover available networks and synchronizes the results into Endpoints owned by the current account.
A Provider maintains Endpoint inventory, but it does not add Endpoints to a Gateway Route. After synchronization, you must still select those Endpoints in the target Gateway and configure priority failover or load balancing.
Current support
| Vendor | Discovery behavior |
|---|---|
| Alchemy | Generates Endpoints for every network in the Gateway catalog |
| QuickNode | Expands account single-chain and multichain inventory across every network in the Gateway catalog |
| Chainstack | Imports EVM, Solana, Bitcoin, TRON, and Litecoin Mainnet nodes from the account inventory |
| dRPC | Generates EVM, Solana Mainnet/Devnet, Bitcoin Mainnet, and TRON Mainnet Endpoints |
| Tenderly | Generates EVM Endpoints only where Tenderly provides Node RPC; BNB Mainnet/Testnet are excluded |
Each integration synchronizes the intersection of the networks supported by the vendor and Supported networks. Alchemy, QuickNode, and Chainstack generate both JSON-RPC and native HTTP API Endpoints for TRON. dRPC generates only the TRON JSON-RPC Endpoint. dRPC Solana requires a Premium plan at the vendor.
The vendor credential is used to access the vendor account or configure the authentication required by synchronized Endpoints. Use a valid credential from the vendor dashboard, and never put it in source code, logs, or public links.
Create and sync a Provider
1. Create the connection
Open Providers in the dashboard, select New provider, and configure:
- Name: identifies this connection in the dashboard;
- Vendor: Alchemy, QuickNode, Chainstack, dRPC, or Tenderly; it cannot be changed after creation;
- API key / secret: the credential issued by the vendor;
- Automatic sync: whether to refresh Endpoint inventory on a schedule;
- Sync interval: every hour, 6 hours, 12 hours, day, 3 days, or week;
- Network filter: controls which networks supported by the selected vendor participate in synchronization.
Automatic sync is off by default. After creation, select Sync now, or enable automatic sync and wait for the scheduled job.
2. Choose the network scope
The three network-filter modes are mutually exclusive:
| Mode | Behavior |
|---|---|
| All networks | Accept every network discovered by the vendor and supported for that Provider integration |
| Only these | Synchronize only the selected chain and network pairs |
| Exclude these | Synchronize discovered results except for the selected pairs |
A filter only narrows vendor discovery; it cannot add support for a new chain or network. Run synchronization again after changing the filter to apply the new scope.
3. Review the result
Each synchronization reports these Endpoint changes:
| Result | Meaning |
|---|---|
| Created | A newly discovered Endpoint was created |
| Updated | Vendor-managed connection details such as URL or authentication changed |
| Restored | A previously archived Endpoint reappeared and became available again |
| Archived | A complete discovery confirmed that the Endpoint left the vendor inventory |
| Skipped | An Endpoint could not be identified, validated, or safely updated |
The Provider page also shows the last synchronization status:
- Never synced: synchronization has not run yet;
- Success: discovery and updates completed;
- Partial: usable results were published, but some Endpoints or vendor catalog data could not be processed completely;
- Failed: discovery failed and no destructive inventory changes were published.
An incomplete discovery does not bulk-archive Endpoints omitted from its response. When vendor metadata is missing for one Endpoint, its existing record is also preserved so a temporary vendor failure does not cause a destructive update.
4. Add Endpoints to a Gateway Route
Open the Provider tab under Endpoints and review the synchronized records. The Provider manages connection details such as chain, network, URL, and authentication, so these fields cannot be edited like a manually created Endpoint.
Then open the Gateway for the same chain and network and add the Endpoint to its default JSON-RPC Route. An Endpoint participates in routing, load balancing, and failover only after a Route references it.
Disable, update, or delete a Provider
- Disable a Provider: stops manual and automatic synchronization while retaining synchronized Endpoints. Re-enable it to resume synchronization.
- Replace the credential: saving a new value immediately replaces the previous credential. The next synchronization updates Provider-managed Endpoint authentication from discovery results.
- Delete a Provider: stops management and detaches its Endpoints. By default, each Endpoint retains its URL, authentication, and configuration.
- Also delete unreferenced Endpoints: deletes only Endpoints unused by Gateway Routes. Referenced Endpoints are always retained and detached from the Provider.
When a complete synchronization finds that an Endpoint has disappeared, the system tries to archive it. An Endpoint referenced by a Route is not archived and is reported as skipped instead.
Troubleshooting
Synchronization fails
Confirm that the Provider is enabled, its credential is valid, and the vendor management API is reachable. A temporary vendor catalog or account API failure can produce a failed or partial result; existing Endpoints are not bulk-deleted after an incomplete discovery.
No Endpoints are discovered
Check whether the network filter excludes the target and whether the network appears in Supported networks. QuickNode requires an Admin API key that can list account Endpoints and their per-network URLs. Chainstack requires a Platform API key that can read both v1 node connection details and v2 node network metadata. dRPC Solana networks require a Premium plan.
Synchronization succeeds but the Gateway has no usable Endpoint
Provider synchronization creates or updates Endpoints; it does not change Gateway Routes. Open the target Gateway, add a synchronized Endpoint with a matching chain and network to the Route, and confirm that the Endpoint is enabled.
An Endpoint is archived or skipped
Archived means a complete synchronization confirmed that the Endpoint was absent from vendor inventory. A later synchronization restores it if it reappears. Skipped usually means missing vendor metadata, URL validation, or Route-reference protection prevented a change; expand the synchronization details for the specific error.