QuickNode
The QuickNode integration reads the Endpoints that already exist in your QuickNode account and imports them, including multichain Endpoints, which are expanded into one Gateway Endpoint per network.
Credential
Provide a QuickNode Admin API key.
The key is sent to the QuickNode account API during discovery. Grant it permission to list account Endpoints, read the chain catalog, and read the per-network URLs of a multichain Endpoint.
The Endpoint credential itself is not taken from this key. It is extracted from the Endpoint URL that QuickNode returns: the secret path segment is replaced with a placeholder and applied as a path credential. When an Endpoint URL carries no secret path segment, the Endpoint is created without authentication.
Network coverage
| Chain | Networks | Transports |
|---|---|---|
| Ethereum | Mainnet, Sepolia | JSON-RPC |
| Polygon | Mainnet, Amoy | JSON-RPC |
| BNB Smart Chain | Mainnet, Testnet | JSON-RPC |
| Arbitrum | Mainnet, Sepolia | JSON-RPC |
| Optimism | Mainnet, Sepolia | JSON-RPC |
| Base | Mainnet, Sepolia | JSON-RPC |
| Solana | Mainnet Beta, Devnet | JSON-RPC |
| Bitcoin | Mainnet, Testnet | JSON-RPC |
| Litecoin | Mainnet, Testnet | JSON-RPC |
| TRON | Mainnet, Nile | JSON-RPC, native HTTP API |
The table is the upper bound. What is actually synchronized is the intersection of this table, Supported networks, and the Endpoints present in your QuickNode account. TRON Endpoints are imported twice, once for JSON-RPC and once for the native HTTP API.
Synchronization behavior
Discovery pages through the account Endpoint list and accepts only Endpoints whose vendor status is active. A multichain Endpoint triggers a second call that fetches its per-network URLs, and the credential shared across those URLs is derived from the path segments they have in common.
Synchronization imports active Endpoints and multichain Endpoints with one consistent shared credential path. Usable Endpoints are published while an incomplete result preserves existing inventory.
Verification checklist
- Use a QuickNode Admin API key with Endpoint and chain-catalog read permissions.
- Keep the required Endpoints active in QuickNode and include their networks in the Provider selection.
- Review Activity, compare the synchronized inventory with QuickNode, and confirm each Endpoint’s vendor access controls.
See the QuickNode RPC integration overview for how synchronized Endpoints are used in Routes. Return to the Providers overview for the shared synchronization workflow and Endpoint lifecycle.