Find the endpoint for your network, confirm it supports the transport you need, and check whether it serves archive data. The EVM RPC endpoint path ends in the EVM chain ID:
https://rpc.graphops.xyz/v1/evm/<chainId>
wss://rpc.graphops.xyz/v1/evm/<chainId>Authenticate requests with an organization-scoped API key. See Authentication for header and route-token options.
Endpoint preview
Replace placeholders with your identifier and API key before making requests.
Supported endpoints
| Network | Network ID (CAIP-2) | HTTPS endpoint | WebSocket endpoint | Archive |
|---|---|---|---|---|
| Ethereum Mainnet | eip155:1 | https://rpc.graphops.xyz/v1/evm/1 | wss://rpc.graphops.xyz/v1/evm/1 | Yes |
| Ethereum Sepolia | eip155:11155111 | https://rpc.graphops.xyz/v1/evm/11155111 | wss://rpc.graphops.xyz/v1/evm/11155111 | Yes |
| Gnosis | eip155:100 | https://rpc.graphops.xyz/v1/evm/100 | wss://rpc.graphops.xyz/v1/evm/100 | Yes |
| Base | eip155:8453 | https://rpc.graphops.xyz/v1/evm/8453 | wss://rpc.graphops.xyz/v1/evm/8453 | Yes |
| Arbitrum One | eip155:42161 | https://rpc.graphops.xyz/v1/evm/42161 | wss://rpc.graphops.xyz/v1/evm/42161 | Yes |
| Arbitrum Sepolia | eip155:421614 | https://rpc.graphops.xyz/v1/evm/421614 | wss://rpc.graphops.xyz/v1/evm/421614 | Yes |
| Bitcoin Mainnet | bip122:000000000019d6689c085ae165831e93 | https://rpc.graphops.xyz/v1/bitcoin/mainnet | — | — |
| Bitcoin Signet | bip122:00000008819873e925422c1ff0f99f7c | https://rpc.graphops.xyz/v1/bitcoin/signet | — | — |
This catalog includes currently published mainnet and testnet endpoints. Copy the generated endpoint for your network when configuring a connection. The CAIP-2 ID identifies the network; the endpoint contains its service-specific routing reference.
Bitcoin endpoints
Bitcoin RPC uses HTTPS and a network name instead of an EVM chain ID:
/v1/bitcoin/<network>[/API_KEY]Choose a Bitcoin network from the catalog above. Authenticate with an
Authorization: Bearer <GRAPHOPS_API_KEY> header or append the key to the endpoint path.
Network notes
| Network | Notes |
|---|---|
| Ethereum Mainnet | Use safe, finalized, or explicit block references when user-facing workflows need more stability than latest. See Consistency and finality. |
| Arbitrum One | L2 transaction visibility and finality can differ from Ethereum L1. Use explicit block references for multi-call workflows. |
| Base | L2 transaction visibility and finality can differ from Ethereum L1. Use explicit block references for multi-call workflows. |
Archive support
Check the Archive column above for each network’s published capability. Historical state reads and broad log backfills are heavier than current-state reads. Use bounded ranges and split large jobs into resumable chunks.