# How to connect beaconcha.in to Hermes Agent (paste one key, 37 tools) > Connect beaconcha.in to Hermes with ClawLink: paste your beaconcha.in key once and 37 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/beaconchain Most guides for giving Hermes Agent beaconcha.in access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical beaconcha.in setup: pair once in the browser and your always-on Hermes agent can act on beaconcha.in for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to beaconcha.in. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect beaconcha.in** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect beaconchain # connect beaconcha.in (browser OAuth) npx -y @useclawlink/cli actions beaconchain # list available actions npx -y @useclawlink/cli run beaconchain --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect beaconcha.in in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your beaconcha.in API key once. Verify the connection by asking Hermes: > Pull the relevant data from beaconcha.in, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once beaconcha.in is connected in the dashboard, that agent calls the same 37 beaconcha.in tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## beaconcha.in MCP for Hermes Looking for a beaconcha.in MCP server for Hermes Agent? ClawLink connects beaconcha.in to Hermes Agent and exposes 37 beaconcha.in tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw beaconcha.in integration](https://claw-link.dev/openclaw/beaconchain) works the same way. ## What the Hermes Agent beaconcha.in integration can do 37 beaconcha.in tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 37. ### 30 of 37 beaconcha.in tools for Hermes | Tool | What it does | |---|---| | **Get chart** `beaconchain_get_chart` | Retrieve chart visualizations from beaconcha.in as PNG images | | **Get epoch** `beaconchain_get_epoch` | Retrieve aggregate metrics and status for a beacon chain epoch | | **Get eth store daily** `beaconchain_get_eth_store_daily` | Retrieve ETH.Store daily aggregate metrics for Ethereum validators | | **Get eth1 deposits by tx hash** `beaconchain_get_eth1_deposits_by_tx_hash` | Retrieve all beacon chain validator deposit events associated with a specific execution-layer | | **Get execution address erc20 tokens** `beaconchain_get_execution_address_erc20_tokens` | Retrieve a paginated list of ERC-20 token balances for a specific Ethereum address | | **Get execution block** `beaconchain_get_execution_block` | Retrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain | | **Get execution produced blocks** `beaconchain_get_execution_produced_blocks` | Retrieve execution-layer blocks attributed to one or more producers | | **Get latest state** `beaconchain_get_latest_state` | Retrieve the latest known Ethereum Beacon Chain network state | | **Get network performance** `beaconchain_get_network_performance` | Retrieve aggregated network performance metrics for the Ethereum Beacon Chain | | **Get node health** `beaconchain_get_node_health` | Check the health status of the beaconcha.in explorer service | | **Get queues** `beaconchain_get_queues` | Retrieve current queue metrics for Ethereum Beacon Chain validators | | **Get rocketpool validator** `beaconchain_get_rocketpool_validator` | Retrieve Rocket Pool-specific metadata for validators including minipool status, node fee | | **Get slot** `beaconchain_get_slot` | Retrieve detailed information about an Ethereum Beacon Chain slot | | **Get slot attestations** `beaconchain_get_slot_attestations` | Retrieve all attestations included in the beacon block for a specific slot | | **Get slot attester slashings** `beaconchain_get_slot_attester_slashings` | Retrieve all attester slashing operations included in the beacon block for a specific slot | | **Get slot proposer slashings** `beaconchain_get_slot_proposer_slashings` | Retrieve all proposer slashing operations included in the beacon block for a specific slot | | **Get slot voluntary exits** `beaconchain_get_slot_voluntary_exits` | Retrieve all voluntary exit operations included in the beacon block for a specific slot | | **Get sync committee** `beaconchain_get_sync_committee` | Retrieve the sync committee membership for a given sync period | | **Get validator** `beaconchain_get_validator` | Retrieve detailed information about an Ethereum Beacon Chain validator | | **Get validator attestation efficiency** `beaconchain_get_validator_attestation_efficiency` | Retrieve normalized attestation inclusion effectiveness for one or more validators | | **Get validator attestations** `beaconchain_get_validator_attestations` | Retrieve attestations observed for one or more validators within a bounded epoch window | | **Get validator balance history** `beaconchain_get_validator_balance_history` | Retrieve per-epoch balance history for one or more Ethereum Beacon Chain validators | | **Get validator bls changes** `beaconchain_get_validator_bls_changes` | Retrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators | | **Get validator consensus rewards** `beaconchain_get_validator_consensus_rewards` | Retrieve consensus-layer rewards for one or more validators over multiple lookback windows | | **Get validator daily stats** `beaconchain_get_validator_daily_stats` | Retrieve per-day statistics for a single Ethereum Beacon Chain validator by index | | **Get validator deposits** `beaconchain_get_validator_deposits` | Retrieve execution-layer deposit events for one or more validators | | **Get validator execution rewards** `beaconchain_get_validator_execution_rewards` | Retrieve execution-layer rewards (priority fees and MEV payments) for one or more validators | | **Get validator income history** `beaconchain_get_validator_income_history` | Retrieve a per-epoch income breakdown for one or more validators | | **Get validator leaderboard** `beaconchain_get_validator_leaderboard` | Retrieve the current top 100 validators ranked by 7-day consensus-layer rewards | | **Get validator proposals** `beaconchain_get_validator_proposals` | Retrieve beacon chain blocks proposed by one or more validators within a bounded epoch window | ## Example prompts **Get Chart** > Pull the relevant data from beaconcha.in, summarize it in plain English, and point out anything that needs attention. **Get Epoch** > Pull the relevant data from beaconcha.in, summarize it in plain English, and point out anything that needs attention. **Get Eth Store Daily** > Pull the relevant data from beaconcha.in, summarize it in plain English, and point out anything that needs attention. **Get Eth1 Deposits By Tx Hash** > Pull the relevant data from beaconcha.in, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want beaconcha.in working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the beaconcha.in API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected beaconcha.in account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for beaconcha.in. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right beaconcha.in actions to the runtime in a format your agent can reliably use. | 37 tools for beaconcha.in are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes beaconcha.in to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect beaconcha.in in the browser, and the 37 tools above work from chat. There is no SDK and no config file, and the beaconcha.in key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use beaconcha.in Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### Connection succeeds but no tools appear Reconnect beaconcha.in from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling beaconcha.in tools beaconcha.in tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every beaconcha.in call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### beaconcha.in returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for beaconcha.in has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent beaconcha.in integration? Yes. ClawLink is the fastest way to connect Hermes to beaconcha.in: link your beaconcha.in account once in the browser and Hermes Agent can call the beaconcha.in API through 37 ready-made tools — no custom code or token handling. ### How do I connect beaconcha.in to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect beaconcha.in in the dashboard and Hermes can use it from the next message — no config files, and the beaconcha.in key you paste is stored server-side instead of in your environment. ### How long does it take to connect beaconcha.in to Hermes Agent? About two minutes. Sign in, click Connect next to beaconcha.in in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring beaconcha.in up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want beaconcha.in working from chat. ### Hermes paired but still can't use beaconcha.in Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [PostHog tools](https://claw-link.dev/hermes/posthog) — Track user behavior and feature flags - [DataforSEO](https://claw-link.dev/hermes/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase tools](https://claw-link.dev/hermes/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.