# How to connect Alchemy to Hermes Agent (paste one key, 36 tools) > Connect Alchemy to Hermes with ClawLink: paste your Alchemy key once and 36 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/alchemy Most guides for giving Hermes Agent Alchemy 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 Alchemy setup: pair once in the browser and your always-on Hermes agent can act on Alchemy 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 Alchemy. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Alchemy** — 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 alchemy # connect Alchemy (browser OAuth) npx -y @useclawlink/cli actions alchemy # list available actions npx -y @useclawlink/cli run alchemy --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 Alchemy in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Alchemy API key once. Verify the connection by asking Hermes: > Use Alchemy to compute rarity v3 and walk me through the result in plain English. ### 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 Alchemy is connected in the dashboard, that agent calls the same 36 Alchemy 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). ## Alchemy MCP for Hermes Looking for a Alchemy MCP server for Hermes Agent? ClawLink connects Alchemy to Hermes Agent and exposes 36 Alchemy 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 Alchemy integration](https://claw-link.dev/openclaw/alchemy) works the same way. ## What the Hermes Agent Alchemy integration can do 36 Alchemy 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 36. ### 30 of 36 Alchemy tools for Hermes | Tool | What it does | |---|---| | **Compute rarity v3** `alchemy_compute_rarity_v3` | Compute the rarity of each attribute for a specific NFT based on its collection | | **Get collection metadata** `alchemy_get_collection_metadata` | Get metadata for an NFT collection using its marketplace slug (OpenSea, LooksRare, etc) | | **Get collections for owner** `alchemy_get_collections_for_owner` | Retrieve all NFT collections held by a specified owner address | | **Get contract metadata batch v3** `alchemy_get_contract_metadata_batch_v3` | Retrieve metadata for multiple NFT contracts in a single batch request | | **Get contract metadata v3** `alchemy_get_contract_metadata_v3` | Get the metadata for an NFT contract including name, symbol, total supply, and token type | | **Get contracts for owner v3** `alchemy_get_contracts_for_owner_v3` | Get all NFT contracts owned by an address with contract metadata | | **Get floor price v3** `alchemy_get_floor_price_v3` | Get the floor price for an NFT collection across multiple marketplaces (OpenSea, LooksRare, etc) | | **Get historical prices** `alchemy_get_historical_prices` | Retrieves historical price data for a token over a specified time range with configurable | | **Get nf ts for collection v3** `alchemy_get_nf_ts_for_collection_v3` | Retrieves all NFTs in a collection using OpenSea collection slug or contract address | | **Get nf ts for contract** `alchemy_get_nf_ts_for_contract` | Retrieves all NFTs for a given NFT contract address | | **Get nf ts for owner** `alchemy_get_nf_ts_for_owner` | Get all NFTs currently owned by a given address | | **Get nft contracts by address** `alchemy_get_nft_contracts_by_address` | Retrieve NFT contracts associated with one or more wallet addresses across multiple blockchain | | **Get nft metadata** `alchemy_get_nft_metadata` | Retrieve comprehensive metadata for a specific NFT, including contract details, media URLs | | **Get nft metadata batch** `alchemy_get_nft_metadata_batch` | Retrieve metadata for multiple NFTs in a single request (up to 100 NFTs), including contract | | **Get nft sales v3** `alchemy_get_nft_sales_v3` | Retrieves NFT sales that have occurred through on-chain marketplaces using Alchemy's v3 API | | **Get owners for collection** `alchemy_get_owners_for_collection` | Retrieve all owner addresses for a given NFT collection contract | | **Get owners for contract** `alchemy_get_owners_for_contract` | Get all owners of NFTs in a contract with optional token balances | | **Get owners for nftv3** `alchemy_get_owners_for_nftv3` | Retrieve all owners for a specific NFT using Alchemy's v3 API | | **Get portfolio nf ts by address** `alchemy_get_portfolio_nf_ts_by_address` | Fetch NFTs owned by multiple wallet addresses across different blockchain networks | | **Get prices by symbol** `alchemy_get_prices_by_symbol` | Get current token prices by symbol (e.g., ETH, USDC, BTC) using aggregated CEX and DEX data | | **Get token balances** `alchemy_get_token_balances` | Retrieves ERC20 token balances for a specified Ethereum address | | **Get token balances by address** `alchemy_get_token_balances_by_address` | Get token balances for wallet addresses across multiple networks using Alchemy's Portfolio API | | **Get token metadata** `alchemy_get_token_metadata` | Retrieves metadata for an ERC-20 token on Ethereum mainnet, including its name, symbol | | **Get token prices by address** `alchemy_get_token_prices_by_address` | Retrieves current token prices by contract address and network from decentralized exchanges | | **Get tokens by address** `alchemy_get_tokens_by_address` | Fetch fungible tokens (native, ERC-20, SPL) for multiple wallet addresses across networks | | **Get transaction count** `alchemy_get_transaction_count` | Retrieves the number of transactions sent from a specific address (also known as the nonce) | | **Get transactions history by address** `alchemy_get_transactions_history_by_address` | Get transaction history for wallet addresses across multiple networks using Alchemy's Data API | | **Is airdrop** `alchemy_is_airdrop` | Check if a specific NFT token is marked as an airdrop | | **Is airdrop nft** `alchemy_is_airdrop_nft` | Determine whether an NFT was airdropped to the owner address | | **Is holder of collection** `alchemy_is_holder_of_collection` | Check if a wallet address owns any token from a specific NFT collection | ## Example prompts **Compute Rarity V3** > Use Alchemy to compute rarity v3 and walk me through the result in plain English. **Get Collection Metadata** > Pull the relevant data from Alchemy, summarize it in plain English, and point out anything that needs attention. **Get Collections For Owner** > Pull the relevant data from Alchemy, summarize it in plain English, and point out anything that needs attention. **Get Contract Metadata Batch V3** > Pull the relevant data from Alchemy, 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 Alchemy working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Alchemy API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Alchemy 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 Alchemy. | 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 Alchemy actions to the runtime in a format your agent can reliably use. | 36 tools for Alchemy are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Alchemy 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 Alchemy in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the Alchemy 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 Alchemy 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 Alchemy 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 Alchemy tools Alchemy 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 Alchemy 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. ### Alchemy 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 Alchemy 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 Alchemy integration? Yes. ClawLink is the fastest way to connect Hermes to Alchemy: link your Alchemy account once in the browser and Hermes Agent can call the Alchemy API through 36 ready-made tools — no custom code or token handling. ### How do I connect Alchemy 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 Alchemy in the dashboard and Hermes can use it from the next message — no config files, and the Alchemy key you paste is stored server-side instead of in your environment. ### How long does it take to connect Alchemy to Hermes Agent? About two minutes. Sign in, click Connect next to Alchemy in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Alchemy 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 Alchemy working from chat. ### Hermes paired but still can't use Alchemy 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 - [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.