Skip to main content
The V2 API is the recommended API for all new integrations. It offers richer data, flexible validator selectors, cursor-based pagination, and exclusive features like BeaconScore® and entity benchmarking. The V1 API remains available but no new features will be added to V1.

Build with AI

Give your AI assistant or coding agent the full beaconcha.in documentation, so it answers from the current API reference instead of guessing endpoints and fields. One line connects Cursor, Claude, or any other MCP client to our docs server:

MCP Server

Connect Cursor, Claude Desktop, or any MCP-compatible tool directly to the docs.

llms.txt

A complete documentation index for any LLM that follows the llms.txt standard.

skill.md

Capabilities, workflows, and staking context written for AI agents.

Set up AI Integration

Step-by-step setup for every tool, and what your assistant can do once connected

Pricing

*Prices shown are for annual billing, excluding VAT
  • Free Trial: Test the API with a 30-day free trial. The trial does not auto-renew; access ends after 30 days unless you upgrade. Start your free trial and create an API key.
  • Access: API endpoints require an API key. Free Trial and paid users have access to both V1 and V2 APIs.
  • Pro 💎 features: available for users on the Scale and Enterprise plans.
  • Attribution: See API Terms and Conditions for details.

Attribution Requirements

If you use beaconcha.in API data in your application or website, please follow these attribution guidelines:

BeaconScore®

After an agreement the BeaconScore® badge may be required. See API Terms and Conditions for details.
BeaconScore®

Powered by beaconcha.in

After an agreement the “Powered by beaconcha.in” logo may be required. See API Terms and Conditions for details.
Powered by beaconcha.in

License Materials

Download official BeaconScore® and “Powered by beaconcha.in” badges in SVG format
For full terms and conditions, see our BeaconScore® License.

API Keys

API keys can be obtained in the user portal and must be included in requests either as a query string parameter or in the request header.
V1 and V2 APIs use the same authentication method. A single API key is valid for all endpoints.

Quick Start — Your First Request

The simplest V2 API call is the Chain State endpoint, which returns the current state of the Ethereum network with a single field in the request body:
All V2 API endpoints use the POST method with a JSON request body. The chain field ("mainnet" or "hoodi") selects the network and defaults to "mainnet" on most endpoints.

Full Example — Validator Rewards

This example uses the Rewards endpoint to get validator rewards data.

Request

Response

View Full API Documentation

See all parameters, response fields, and try the Rewards endpoint