Chainstack

The Chainstack integration imports the nodes that already exist in your Chainstack account. It reads connection details and network metadata from two different Chainstack API versions and combines them into Endpoints.

Credential

Provide a Chainstack Platform API key.

The key is sent as a bearer credential during discovery. Grant it access to both the v1 node connection details and the v2 node network metadata so every node can be mapped to a chain and network.

The Endpoint credential is taken from the node record itself, either from its authentication key or from the last path segment of its HTTPS endpoint, and applied as a path credential. A node whose URL carries no such segment produces an Endpoint without authentication.

Network coverage

The table is the complete Chainstack integration scope; use a manual Endpoint for Litecoin Testnet. Only nodes that exist in your Chainstack account are imported. TRON nodes produce both a JSON-RPC and a native HTTP API Endpoint.

Synchronization behavior

Discovery pages through the node list and accepts only nodes whose vendor status is running. Each page of results is matched against the v2 metadata that provides the node’s protocol and network.

Discovery combines the v1 connection details with v2 metadata and preserves existing inventory during an incomplete result. Pagination remains on Chainstack’s API host.

Verification checklist

• Use a Platform API key that reads both node connection details and network metadata.
• Keep imported nodes in the running state and include their networks in the Provider selection.
• Add Litecoin Testnet as a manual Endpoint when required.
• Confirm every node’s access settings and credential path in Chainstack, then run its Gateway health check.

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