# Base RPC, Subgraphs and Substreams

Read Base state, submit signed transactions and subscribe to node events through GraphOps RPC over HTTPS and WebSocket. Query indexed Base data through GraphQL Subgraphs, including your own Managed Subgraphs. Backfill and stream Base blocks into your own storage with Substreams.

[Create account](https://platform.graphops.xyz/auth/register)[Network reference](https://docs.graphops.xyz/rpc/networks)

Chain ID

8453

CAIP-2 ID

eip155:8453

Network type

Mainnet

Services

RPC, Subgraphs, Substreams

## GraphOps services on Base

One API key from your organization can include every service you use, and all of them draw from the organization's credit balance.

### RPC

Send JSON-RPC requests over HTTPS, or open a WebSocket for subscriptions. Archive data is available: historical state, such as eth_call at a past block, and historical event logs. Execution traces are available, such as the internal calls of a transaction or a block.

HTTPS

https://rpc.graphops.xyz/v1/evm/8453

WebSocket

wss://rpc.graphops.xyz/v1/evm/8453

[GraphOps RPC](https://graphops.xyz/services/rpc/) [RPC network reference](https://docs.graphops.xyz/rpc/networks)

### Subgraphs

Query any Subgraph that The Graph Network serves on Base by Deployment CID or Graph Network Subgraph ID. Managed indexing runs on Base: publish a Managed Subgraph and GraphOps indexes it. Managed Subgraphs need a monthly plan.

Manifest network

base

[GraphOps Subgraphs](https://graphops.xyz/services/subgraphs/) [Subgraph network reference](https://docs.graphops.xyz/subgraphs/networks)

### Substreams

Backfill Base history and continue with a live gRPC stream of package output. Your consumer commits the data and saves its cursor. Packages for Base declare base or base-mainnet as their network.

gRPC

https://8453.evm.substreams.graphops.xyz

[GraphOps Substreams](https://graphops.xyz/services/substreams/) [Substreams network reference](https://docs.graphops.xyz/substreams/networks)

## Base network details

Use these identifiers to name Base in requests, manifests and package configuration.

EVM chain ID

8453

CAIP-2 network ID

eip155:8453

Network type

Mainnet

Subgraph manifest network

base

Other network names

base-chain base-mainnet evm-8453

Block explorer

[basescan.org](https://basescan.org/)

## Make a first Base request

This request reads the latest Base block number with eth_blockNumber. Create an API key that includes RPC in your organization and export it as GRAPHOPS_API_KEY. The example sends it in the Authorization header.

[RPC quickstart](https://docs.graphops.xyz/rpc/getting-started) [Authentication](https://docs.graphops.xyz/rpc/authentication)

## Pricing

Usage on Base draws credits at the same rates as on every other network. Your monthly plan sets the price per credit.

[Size a plan and estimate your usage](https://graphops.xyz/pricing/)

[Live pricing: plan prices, extra credits and every usage rate](https://graphops.xyz/pricing.md)

## Base questions

What is the Base chain ID?

Base is a mainnet with EVM chain ID 8453. Its CAIP-2 network ID is eip155:8453.

What is the GraphOps Base RPC endpoint?

Send HTTPS JSON-RPC requests to https://rpc.graphops.xyz/v1/evm/8453, and open WebSocket connections to wss://rpc.graphops.xyz/v1/evm/8453. Authenticate with an API key from your organization that includes RPC, in the Authorization header or as a route token at the end of the path.

Does GraphOps Base RPC serve archive data?

Yes. Historical state, such as eth_call at a past block, and historical event logs are available on Base.

Does GraphOps Base RPC support tracing?

Yes. Base RPC serves execution traces, such as the internal calls of a transaction or a block.

Which network name do Base Subgraphs use?

Subgraphs that index Base declare network: base in their manifest.

Can GraphOps index my own Subgraph on Base?

Yes. Managed indexing runs on Base, so you can deploy a Managed Subgraph that GraphOps indexes. Managed Subgraphs need a monthly plan.

What is the GraphOps Base Substreams endpoint?

Stream Base packages from https://8453.evm.substreams.graphops.xyz over gRPC. Packages for Base declare base or base-mainnet as their network.

## Related networks

[All supported networks](https://graphops.xyz/networks/)

- [Testnet · Chain ID 84532

### Base Sepolia Testnet

eip155:84532

- Subgraphs

View Base Sepolia Testnet](https://graphops.xyz/networks/base-sepolia-testnet/)

- [Mainnet · Chain ID 1

### Ethereum Mainnet

eip155:1

- RPC  · archive, tracing

- Subgraphs  · managed indexing

- Substreams

View Ethereum Mainnet](https://graphops.xyz/networks/ethereum-mainnet/)

- [Testnet · Chain ID 11155111

### Ethereum Sepolia

eip155:11155111

- RPC  · archive

- Subgraphs  · managed indexing

View Ethereum Sepolia](https://graphops.xyz/networks/ethereum-sepolia/)

- [Mainnet · Chain ID 100

### Gnosis

eip155:100

- RPC  · archive

- Subgraphs  · managed indexing

View Gnosis](https://graphops.xyz/networks/gnosis/)

## Start building on Base.

Create an organization, choose your monthly credits, then create an API key that includes the services you need.

[Create account](https://platform.graphops.xyz/auth/register)[Discuss your project](https://graphops.xyz/contact/#enterprise)
