Running nodes only
Discovery accepts nodes that currently report Chainstack's running status and skips other vendor states.
Chainstack integration
Import Chainstack nodes into RPC Gateway
Read existing running nodes from your Chainstack account, combine connection details with network metadata, and publish matching Gateway Endpoints.
Integration details
Discovery combines node connection details from Chainstack's v1 API with protocol and network metadata from its v2 API.
- Credential
- Chainstack Platform API key
- Network scope
- Supported networks represented by running nodes in your account
- Transport
- JSON-RPC, plus TRON native HTTP API
How Chainstack synchronization works
Litecoin Testnet gap
Chainstack synchronization covers Litecoin Mainnet; Litecoin Testnet can be added as a manual Endpoint.
Node-level credentials
Endpoint credentials come from the node record or its HTTPS path rather than the Platform API key used for discovery.
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 Chainstack integration guideExplore RPC failover
Next step
Bring Chainstack nodes into your Gateway
Add a Platform API key that can read node connections and network metadata, then review each synchronized Endpoint.