Beaconchain is a platform providing real-time data and analytics for the Ethereum 2.0 Beacon Chain, offering insights into validators, blocks, and network performance.
Beaconchain is a platform providing real-time data and analytics for the Ethereum 2.0 Beacon Chain, offering insights into validators, blocks, and network performance. On Nagent, beaconcha.in is exposed as a fully-configurable analytics integration that any agent can call — 37 actions, and API key authentication. No code is required to wire beaconcha.in into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use beaconcha.in to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire beaconcha.in into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against beaconcha.in, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BEACONCHAIN_GET_CHARTRetrieve chart visualizations from beaconcha.in as PNG images. Use when you need visual representations of Ethereum Beacon Chain data like validator counts, staked ether, network liveness, or block statistics.
Input parameters
Chart type to retrieve. Specifies which visualization to generate from beaconcha.in charts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_EPOCHRetrieve aggregate metrics and status for a beacon chain epoch. Use this tool to fetch epoch-level statistics including validator counts, balances, participation rates, block counts, and various operations (slashings, deposits, exits). Supports lookup by epoch number or keywords 'latest' or 'finalized'.
Input parameters
The epoch to fetch. Provide an integer epoch number (>= 0), or one of the keywords `latest` or `finalized`.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_ETH1_DEPOSITS_BY_TX_HASHRetrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash. Use this tool to inspect deposit transactions and verify deposit parameters like amount, public key, and withdrawal credentials. Returns an empty array if the transaction contains no deposit events.
Input parameters
Execution-layer transaction hash to inspect. Provide tx hash as a 0x-prefixed hex string (64 hex characters after 0x, e.g., '0x3629639fe74ef981ff72ba2678130c700b779964e6c22fe42201445084e9d343').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_ETH_STORE_DAILYRetrieve ETH.Store daily aggregate metrics for Ethereum validators. Use this to analyze the average financial return validators achieved over a specific 24-hour period, including APR metrics, consensus/execution layer rewards, and balance aggregates.
Input parameters
The beaconchain-day to fetch. Provide an integer day index (>= 0, e.g., '0', '100', '1000'), or the keyword 'latest' for the most recently computed day.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_EXECUTION_ADDRESS_ERC20_TOKENSRetrieve a paginated list of ERC-20 token balances for a specific Ethereum address. Use offset and limit query parameters for pagination. Returns token contract address, balance in token units, and token symbol for each ERC-20 token held by the address.
Input parameters
Maximum number of tokens to return per page. Allowed range is 1 to 200.
Number of items to skip from the start of the result set. Use 0 for the first page.
Ethereum account address to query. Provide a 0x-prefixed, 20-byte hex string (40 hexadecimal characters after 0x).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_EXECUTION_BLOCKRetrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain. Use this tool to look up execution block details including block hash, timestamp, rewards, gas usage, transaction counts, and consensus information. Supports querying up to 100 blocks in a single request by providing block numbers as a comma-separated list. Returns an array of execution block data. If a requested block number is not found, it will be omitted from the results.
Input parameters
One or more execution block numbers as a comma-separated list (e.g., '17000000' or '17000000,17000001,17000002'). Each item must be a non-negative integer. A maximum of 100 block numbers is allowed per request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_EXECUTION_PRODUCED_BLOCKSRetrieve execution-layer blocks attributed to one or more producers. Use this tool to query blocks produced by specific fee recipients, proposer indices, or validator public keys. Supports comma-separated lists to query multiple producers. Returns block details including gas usage, fees, transactions, and timestamps.
Input parameters
Sort order for execution blocks.
Maximum number of blocks to return. Allowed range is 1 to 100.
Number of items to skip from the start of the merged result set. Use 0 for the first page.
Comma-separated list of producers to query. Each item may be: (1) a fee recipient address (0x-prefixed, 20-byte hex, or a valid ENS name), (2) a proposer index (non-negative integer), or (3) a validator public key (0x-prefixed, 48-byte BLS pubkey: 96 hex characters). Provide multiple items by separating them with commas. A maximum of 20 addresses and 100 indices/pubkeys is accepted per request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_LATEST_STATERetrieve the latest known Ethereum Beacon Chain network state. Returns current slot, epoch numbers, finalized epoch, finality delay indicator, syncing status, and ETH/USD price along with multi-currency conversion rates. Use this to check current network status and get real-time ETH pricing data.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_NETWORK_PERFORMANCERetrieve aggregated network performance metrics for the Ethereum Beacon Chain. Use this to analyze validator performance across attestations, proposals, and sync committee duties over a specified time window. Returns beacon scores, duty statistics, and finality information.
Input parameters
The Ethereum chain to query. Defaults to 'mainnet'. Use 'hoodi' for Hoodi testnet.
Time range selector specifying the evaluation window for performance metrics.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_NODE_HEALTHCheck the health status of the beaconcha.in explorer service. Returns status of monitoring modules including execution layer data, consensus layer data, services, Redis, app, and API modules. Use this to verify the beaconcha.in explorer is operational before making other API calls.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_QUEUESRetrieve current queue metrics for Ethereum Beacon Chain validators. Use this tool to check activation queue status, exit queue status, withdrawal sweep progress, and chain finality. Returns deposit queue count and balance, exit queue count and balance, estimated processing times, and churn limits.
Input parameters
Specifies the Ethereum network to query. Options: 'mainnet' or 'holesky'. Defaults to 'mainnet' if omitted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_ROCKETPOOL_VALIDATORRetrieve Rocket Pool-specific metadata for validators including minipool status, node fee, smoothing pool status, and RPL stake metrics. Use this to access Rocket Pool protocol data such as minipool addresses, node operator information, commission rates, and reward details. Returns empty data array if the validator is not a Rocket Pool validator.
Input parameters
Comma-separated list (no spaces) of validator identifiers to query. Each identifier may be either: (1) A validator index as a base-10 integer (e.g., '652648'), or (2) A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive). The server resolves public keys to validator indices before querying data. Maximum 100 identifiers allowed. Public keys that cannot be resolved to an existing validator index cause the request to fail with HTTP 400. Duplicate identifiers are de-duplicated internally.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SLOTRetrieve detailed information about an Ethereum Beacon Chain slot. Use this tool to look up slot details including attestations, slashing counts, block roots, execution payload data, validator proposer, graffiti, and sync aggregate information. Supports lookup by slot number, 'latest'/'head' keywords, or block root hash. Returns comprehensive slot data including: attestation count, block roots, epoch info, execution layer details (gas, fees, transactions), proposer info, and withdrawal count.
Input parameters
The slot to fetch. Provide: (1) an integer slot number (>= 0, e.g., '1', '100'), (2) the special tags 'latest' or 'head' for the current slot, (3) or a 0x-prefixed 32-byte block root hash (64 hex characters after 0x, e.g., '0xa1b2c3...').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SLOT_ATTESTATIONSRetrieve all attestations included in the beacon block for a specific slot. Use this tool to get detailed attestation data including committee participation, checkpoint information, and validator indices for attestations in a given slot.
Input parameters
The slot to fetch. Provide an integer slot number (>= 0) or the special tag 'latest' for the most recently processed slot.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SLOT_ATTESTER_SLASHINGSRetrieve all attester slashing operations included in the beacon block for a specific slot. Use this tool to check for attester slashings at a given slot number or the latest processed slot.
Input parameters
The slot to fetch. Provide an integer slot number (>= 0) or the special tag `latest` for the most recently processed slot.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SLOT_PROPOSER_SLASHINGSRetrieve all proposer slashing operations included in the beacon block for a specific slot. Use this tool to check for proposer slashings at a given slot number or the latest processed slot.
Input parameters
The slot to fetch. Provide an integer slot number (>= 0) or the special tag `latest` for the most recently processed slot.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SLOT_VOLUNTARY_EXITSRetrieve all voluntary exit operations included in the beacon block for a specific slot. Use when you need to examine which validators submitted exit requests in a given slot. Returns an empty array if the slot has no voluntary exits.
Input parameters
The slot to fetch. Provide an integer slot number (>= 0).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_SYNC_COMMITTEERetrieve the sync committee membership for a given sync period. Returns a list of 512 validator indices that participate in light-client finality for the specified period. Each sync period spans 256 epochs. Use this to determine which validators have sync committee duties during a specific period.
Input parameters
The sync period to fetch. Provide a non-negative integer period index (e.g., '0', '500', '1000'), or use one of the special tags: 'latest' (current period) or 'next' (the upcoming period if available). Each period spans 256 consecutive epochs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATORRetrieve detailed information about an Ethereum Beacon Chain validator. Use this tool to look up validator status, balance, activation epochs, slashing status, and other details. Supports lookup by validator index or BLS public key. Returns validator data including: current status (active_online, active_offline, pending, exiting, slashed, exited), balance in Gwei, activation/exit epochs, and withdrawal credentials.
Input parameters
Validator identifier. Accepts: (1) Validator index as a number string (e.g., '0', '1', '100'), or (2) BLS public key with 0x prefix (96 hex characters, e.g., '0xa1d1ad07143535...').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_ATTESTATION_EFFICIENCYRetrieve normalized attestation inclusion effectiveness for one or more validators. Use this tool to measure how effectively validators are getting their attestations included in the Beacon Chain. A score of 1.0 indicates perfect effectiveness (100% inclusion), while higher scores indicate lower effectiveness (max 2.0 for 0% inclusion). Supports lookup by validator index, BLS public key, or a mix of both (comma-separated, maximum 100 validators per request by default).
Input parameters
Comma-separated validator identifiers (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '1', '100', '1,2,3'), or (2) BLS public key with 0x prefix (96 hex characters), or (3) a mix of both. Example: '1,2,3' or '0xa1d1ad07143535...' or '1,0xa1d1ad07143535...,3'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_ATTESTATIONSRetrieve attestations observed for one or more validators within a bounded epoch window. By default, returns data for the last 100 epochs. Use when you need to check validator attestation history, verify attestation performance, or analyze missed attestations.
Input parameters
When true, return a slimmed response that excludes `week`, `week_start`, `week_end`, and `committeeindex` fields from each item.
End epoch for the query window. Defaults to `latest`. Must be within `\[startEpoch, latest\]` when provided.
Start epoch for the query window. Defaults to `latest - 99`. Must be within `\[latest-99, latest\]` and less than or equal to `endEpoch` when provided.
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts validator index as number string (e.g., '1', '100') or BLS public key with 0x prefix (96 hex characters, e.g., '0xa1d1ad07143535...'). For multiple validators, use comma separation: '1,2,3'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_BALANCE_HISTORYRetrieve per-epoch balance history for one or more Ethereum Beacon Chain validators. Use optional query parameters to control the time window (latest_epoch, offset, limit). Returns an array of balance snapshots showing how validator balances changed over time, including both total balance and effective balance. Useful for tracking validator performance and generating historical balance charts.
Input parameters
Number of epochs to return in the window. Allowed range is 1 to 100. Defaults to 100.
Number of epochs to skip backwards from `latest_epoch` before starting the window. Must be non-negative and not exceed `latest_epoch`. Defaults to 0.
Most recent epoch to include (inclusive). Defaults to the latest processed epoch. Must be less than or equal to the latest processed epoch.
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '1', '2', '100'), (2) BLS public key with 0x prefix (96 hex characters), or (3) Comma-separated list of indices/pubkeys (e.g., '1,2,3' or 'pubkey1,pubkey2').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_BLS_CHANGESRetrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators. Use this tool to check if validators have changed their withdrawal credentials from BLS (0x00) to execution-layer addresses (0x01).
Input parameters
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '1', '2', '100'), or (2) BLS public key with 0x prefix (96 hex characters). Multiple identifiers can be combined (e.g., '1,2,3' or '1,0xa1d1ad0714...,100').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_CONSENSUS_REWARDSRetrieve consensus-layer rewards for one or more validators over multiple lookback windows. Returns reward totals for the last 1, 7, 31, and 365 days, plus cumulative totals when available. All amounts are returned in gwei. Supports lookup by validator index or BLS public key.
Input parameters
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '1', '2', '3'), or (2) BLS public key with 0x prefix (96 hex characters). For multiple validators, use comma separation (e.g., '1,2,3').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_DAILY_STATSRetrieve per-day statistics for a single Ethereum Beacon Chain validator by index. Returns daily balance snapshots (start/end/min/max), duty counts (proposed/missed blocks, attestations), and deposit/withdrawal activity. Use this tool to analyze validator performance over time, track balance changes, and identify issues like missed duties or slashing events. Supports filtering by day range using `start_day` and `end_day` parameters.
Input parameters
Validator index to query. Must be a non-negative integer (>= 0).
Last day index to include (inclusive). Defaults to the latest exported day when omitted.
First day index to include (inclusive). Must be less than or equal to `end_day`. When omitted, the API returns all days up to `end_day`.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_DEPOSITSRetrieve execution-layer deposit events for one or more validators. Use when you need to check deposit history, verify deposit amounts, or audit withdrawal credentials for validators.
Input parameters
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts validator index as number string (e.g., '1', '100') or BLS public key with 0x prefix (96 hex characters, e.g., '0xa1d1ad07143535...'). For multiple validators, use comma separation: '1,2,3'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_EXECUTION_REWARDSRetrieve execution-layer rewards (priority fees and MEV payments) for one or more validators. Values are reported in wei and include reward totals for the last 1, 7, 31, and 365 days, plus cumulative rewards since genesis when available. Accepts up to 100 validator identifiers.
Input parameters
Comma-separated validator indices and/or public keys (maximum 100 items). Example: '1,2,3' or '0xa1d1ad07143535...,100,200'. Accepts validator index as a number string or BLS public key with 0x prefix (96 hex characters).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_INCOME_HISTORYRetrieve a per-epoch income breakdown for one or more validators. Returns consensus-layer rewards/penalties in gwei and execution-layer tips in wei. Use this to analyze validator earnings over time, including attestation rewards, proposer rewards, penalties, and MEV/tips.
Input parameters
Number of epochs to return in the window. Allowed range is 1 to 100. Defaults to 100.
Number of epochs to skip backwards from `latest_epoch` before starting the window. Must be non-negative and not exceed `latest_epoch`. Default is 0.
Most recent epoch to include (inclusive). Defaults to the latest finalized epoch. Must be less than or equal to the latest finalized epoch at request time.
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '1', '2', '100'), or (2) BLS public key with 0x prefix (96 hex characters), or (3) Multiple values comma-separated (e.g., '1,2,3' or '1,0xa1d1ad...,100').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_LEADERBOARDRetrieve the current top 100 validators ranked by 7-day consensus-layer rewards. Returns performance metrics including 1-day, 7-day, 31-day, 365-day, and total rewards in Gwei for each validator. Use this to identify the highest-performing validators on the Ethereum Beacon Chain over the past week.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_PROPOSALSRetrieve beacon chain blocks proposed by one or more validators within a bounded epoch window. By default, returns proposals from the last 100 epochs. Use this to get proposal history for validators by their indices or public keys.
Input parameters
Upper bound for the epoch window (inclusive). Results include proposals from epochs in the range \[epoch-100, epoch\]. Defaults to the latest processed epoch when omitted. Must be a non-negative integer.
Comma-separated validator indices and/or public keys (maximum 100 items by default). Each identifier must be either a validator index (base-10 integer) or a 48-byte BLS public key as 0x-prefixed hex (96 hex characters after 0x) or without the 0x prefix.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATORS_BY_DEPOSIT_ADDRESSRetrieve validators that have made deposits from a specific execution-layer address. Supports ENS names which are resolved server-side. Returns validator public keys, signature validity, and validator indices for all deposits from the address.
Input parameters
Maximum number of records to return. Allowed range is 1 to 2000. Defaults to 2000.
Number of items to skip from the start of the result set. Use 0 for the first page.
Execution-layer address whose deposit transactions you want to inspect. Provide a 0x-prefixed, 20-byte hex string (40 hex characters after 0x). ENS names are also accepted and resolved server-side.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATORS_BY_WITHDRAWAL_CREDENTIALSRetrieve validators whose withdrawal credentials match the provided value or execution-layer address. Use this tool to find all validators associated with a specific withdrawal credential (32-byte hex) or Ethereum address (20-byte hex). ENS names are supported for address lookups. Results are paginated using limit and offset parameters.
Input parameters
Maximum number of validators to return. Defaults to 10. Allowed range is 1 to 200 for standard users; higher limits may be available to premium accounts.
Number of items to skip from the start of the result set. Use 0 for the first page.
Withdrawal credentials (32 bytes; 0x-prefixed hex) or an execution-layer address (0x-prefixed, 20-byte hex). ENS names are accepted for the address form.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATORS_PROPOSAL_LUCKRetrieve proposal luck statistics for one or more Ethereum Beacon Chain validators. Use this to analyze how lucky validators have been with block proposals compared to expected rates.
Input parameters
Comma-separated list (no spaces) of validator identifiers. Each identifier must be either: (1) A validator index as a base-10 integer (e.g., '652648'), or (2) A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive). Maximum 100 identifiers allowed (server-enforced).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATORS_QUEUERetrieve current queue metrics for validators on the Ethereum Beacon Chain. Returns counts and total effective balances for validators awaiting activation and validators scheduled to exit. Use this to monitor validator queue status and network entry/exit activity.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_GET_VALIDATOR_WITHDRAWALSRetrieve withdrawal operations attributed to one or more validators within a bounded epoch window. Use this tool to fetch historical withdrawal data for validators on the Ethereum Beacon Chain. The API returns withdrawals from up to 100 epochs (defaulting to the most recent 100 epochs if no epoch is specified).
Input parameters
Upper bound (inclusive) for the 100-epoch window used to fetch withdrawals. Defaults to the latest processed epoch when omitted. Must be a non-negative integer. The API will return withdrawals from (epoch - 99) to epoch (a 100-epoch window).
Comma-separated validator indices and/or public keys (maximum 100 items by default). Accepts: (1) Validator index as a number string (e.g., '100', '1,2,3'), or (2) BLS public key with 0x prefix (96 hex characters), or (3) a mix of both separated by commas.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_POST_VALIDATORSRetrieve validator information using a JSON request body for multiple validators. Use this when the list of identifiers is too long for the GET path parameter (up to 100 identifiers). Supports lookup by validator indices or BLS public keys. Returns validator data including status, balance, activation/exit epochs, slashing status, and withdrawal credentials.
Input parameters
Comma-separated list (no spaces) of validator identifiers. Each identifier must be either: (1) A validator index as a base-10 integer (e.g., '652648'), or (2) A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive). The server resolves public keys to validator indices before querying data. Maximum 100 identifiers allowed. Identifiers that cannot be parsed or resolved result in HTTP 400.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BEACONCHAIN_RESOLVE_ENSResolve ENS (Ethereum Name Service) names to addresses and vice versa. Use this tool to perform bidirectional lookups between ENS domain names and Ethereum addresses. Accepts either an ENS name (e.g., 'vitalik.eth') or an Ethereum address and returns the corresponding mapping.
Input parameters
ENS domain name or Ethereum address to resolve. Accepts: (1) ENS name (e.g., 'vitalik.eth'), or (2) Ethereum address with 0x prefix (e.g., '0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045'). Provides bidirectional resolution between ENS names and Ethereum addresses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 41 agents privately built on Nagent that already use beaconcha.in.
Build on Nagent
Connect beaconcha.in to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find beaconcha.in, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, beaconcha.in is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once beaconcha.in is connected, you configure its 37 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop beaconcha.in steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a beaconcha.in event fires, the agent kicks off automatically.
Every beaconcha.in action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While beaconcha.in ships with 37 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching beaconcha.in together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build beaconcha.in-based workflows tailored to your business.