Berachain
Berachain is a high-performance EVM-identical Layer 1 blockchain built on BeaconKit consensus with a novel Proof-of-Liquidity (PoL) economic model that routes block rewards into productive liquidity via Reward Vaults. Mainnet launched in early 2025 (chain ID 80094) with a Bepolia testnet (chain ID 80069). Developer surfaces include public JSON-RPC at rpc.berachain.com, BeaconKit consensus client, EVM execution via Bera-Reth and Bera-Geth, Berascan block explorer, indexers (Goldsky, Envio), and dApps such as BEX (DEX) and Bend / Honey.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Berachain the way a machine reads it — 14 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Berachain scores 29.1/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Berachain
Each block below is one kind of artifact we hold for Berachain. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Berachain Mainnet JSON-RPC
Public Ethereum-compatible JSON-RPC endpoint for Berachain mainnet (chain ID 80094). Supports the standard eth_* method set used by web3 clients, wallets, and indexers.
Berachain Bepolia Testnet JSON-RPC
Public JSON-RPC endpoint for the Bepolia testnet (chain ID 80069), used for application development and integration testing before deploying to mainnet.
BeaconKit Consensus
Modular consensus layer for Ethereum-based chains used by Berachain to drive validator operations and block production with single-slot finality derived from CometBFT.
Bera-Reth Execution Client
Primary Berachain execution client based on Reth, providing Ethereum-equivalent EVM execution and JSON-RPC for node operators.
Bera-Geth Execution Client
Berachain execution client based on Go-Ethereum, offered as a Geth-compatible alternative to Bera-Reth for node operators.
Proof of Liquidity Protocol
Berachain's economic coordination layer — Reward Vaults, BGT, and validator boost contracts that turn block emissions into application liquidity rather than passive staking yield.
Berascan Block Explorer
Etherscan-style block explorer for Berachain mainnet — view transactions, blocks, contracts, tokens, and verify Solidity source.
Berascan Bepolia Testnet Explorer
Berascan instance for the Bepolia testnet, supporting transaction lookup and contract verification for testnet deployments.
Berachain Developer Tools
Curated registry of RPC providers, oracles, indexers, wallets, dev IDEs, and SDK packages supported on Berachain.
Berachain Deployed Contracts
Registry of core protocol contract addresses on mainnet and Bepolia — Reward Vaults, BGT, HONEY, BERA wrapper, multicall, deterministic deployers, and staking-pool addresses.
Scroll within the panel for all 10 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Berachain Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Berachain Finops
FINOPSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Berachain — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/berachain · machine-readable index on apis.io