---
title: "Berachain API"
description: "Berachain Core RPC API over HTTPS and WSS"
url: "https://blockreq.com/docs/build/api-reference/berachain/"
---

# Berachain API

Berachain endpoints use the EVM JSON-RPC Core API over HTTPS and WSS.

## Endpoint

| Item | Value |
| --- | --- |
| Network | Berachain Mainnet |
| Protocol | EVM JSON-RPC 2.0 |
| Chain ID | `80094` (`0x138de`) |
| Public HTTPS | `https://berachain-rpc.blockreq.com/v1/rpc/public` |
| Private HTTPS | `https://berachain-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000` |
| Public WSS | `wss://berachain-rpc.blockreq.com/v1/rpc/public` |
| Private WSS | `wss://berachain-rpc.blockreq.com/v1/rpc/BRQ1P0000000000000000000000000000000000000000000000000000000` |

These URLs use the product path `/v1/rpc` plus `/public` or `BRQ1P0000000000000000000000000000000000000000000000000000000`.

## Core Methods

Berachain uses [EVM JSON-RPC Methods](https://blockreq.com/docs/build/api-reference/evm-methods/index.md) for latest-state reads, transactions, logs, and archive state.

Archive and all-history calls such as old-block `eth_call` require provider capability and plan access. BlockReq does not currently document or guarantee `eth_getProof`, `debug_*`, or `trace_*` on Berachain.