# dRPC

> Network coverage, credential requirements, and synchronization behavior of the dRPC Provider integration.

Canonical page: https://rpc.aurpay.net/docs/providers/drpc

The dRPC integration generates load-balancer Endpoints from the dRPC public network catalog and applies your dRPC key as the Endpoint credential.

## Credential

Provide either a dRPC API key or a complete dRPC endpoint URL of the form `https://lb.drpc.live/<network>/<key>`.

When a URL is supplied, the key is extracted from it. Use HTTPS, the `lb.drpc.live` host, one network segment, and one key segment, with no query string or fragment.

The resulting key is written into each synchronized Endpoint as a path credential.

## 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 | JSON-RPC |
| TRON | Mainnet | JSON-RPC |

This integration covers the networks in the table above over JSON-RPC. Use Alchemy, QuickNode, Chainstack, or a manual Endpoint for the TRON native HTTP API and for other Gateway networks.

## Synchronization behavior

Discovery reads the dRPC public network catalog and accepts only entries exposed as JSON-RPC. Generated Endpoint URLs use the form `https://lb.drpc.live/<network>/`, with the key applied as a path credential.

The built-in network table supplies discovery during temporary catalog unavailability. Synchronization creates or updates Endpoints while preserving existing inventory in that mode.

## Verification checklist

- Paste either the bare API key or a complete `https://lb.drpc.live/<network>/<key>` URL.
- Enable every selected network in the dRPC plan and run the synchronized Endpoint health checks.
- Use Alchemy, QuickNode, Chainstack, or a manual `http_api` Endpoint for TRON native HTTP API Routes.

See the [dRPC integration overview](https://rpc.aurpay.net/integrations/drpc) for how synchronized Endpoints are used in Routes. Return to the [Providers overview](https://rpc.aurpay.net/docs/providers.md) for the shared synchronization workflow and Endpoint lifecycle.