# How to connect Coinbase Wallet to Hermes Agent (no API keys) > Connect Coinbase Wallet to Hermes with ClawLink in one click — 6 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/hermes/coinbase-wallet Most guides for giving Hermes Agent Coinbase Wallet 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 Coinbase Wallet setup: pair once in the browser and your always-on Hermes agent can act on Coinbase Wallet 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 Coinbase Wallet. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Coinbase Wallet** — 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 coinbase-wallet # connect Coinbase Wallet (browser OAuth) npx -y @useclawlink/cli actions coinbase-wallet # list available actions npx -y @useclawlink/cli run coinbase-wallet --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 Coinbase Wallet in the [ClawLink dashboard](https://claw-link.dev/dashboard) — a one-click OAuth approval, no API keys. Verify the connection by asking Hermes: > Use Coinbase Wallet to mcp get portfolio 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 Coinbase Wallet is connected in the dashboard, that agent calls the same 6 Coinbase Wallet 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). ## Coinbase Wallet MCP for Hermes Looking for a Coinbase Wallet MCP server for Hermes Agent? ClawLink connects Coinbase Wallet to Hermes Agent and exposes 6 Coinbase Wallet 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 Coinbase Wallet integration](https://claw-link.dev/openclaw/coinbase-wallet) works the same way. ## What the Hermes Agent Coinbase Wallet integration can do 6 Coinbase Wallet tools are ready for Hermes Agent once the account is connected. ### All 6 Coinbase Wallet tools for Hermes | Tool | What it does | |---|---| | **Mcp get portfolio** `coinbase_wallet_mcp_get_portfolio` | Returns total portfolio value and per-asset breakdown for a wallet address | | **Mcp get request status** `coinbase_wallet_mcp_get_request_status` | Poll the status of an approval request by requestId (returned by send, sign, swap, or | | **Mcp get transaction history** `coinbase_wallet_mcp_get_transaction_history` | Returns paginated transaction history in reverse chronological order for a single chain | | **Mcp get wallets** `coinbase_wallet_mcp_get_wallets` | Returns the user's Base Account and all agent wallets with delegation status, spend policy, and | | **Mcp help** `coinbase_wallet_mcp_help` | Returns guidance for helping the user with protocol-specific tasks that aren't directly | | **Mcp search tokens** `coinbase_wallet_mcp_search_tokens` | Search for tokens by symbol or name on a single chain | ## Example prompts **Mcp Get Portfolio** > Use Coinbase Wallet to mcp get portfolio and walk me through the result in plain English. **Mcp Get Request Status** > Use Coinbase Wallet to mcp get request status and walk me through the result in plain English. **Mcp Get Transaction History** > Use Coinbase Wallet to mcp get transaction history and walk me through the result in plain English. **Mcp Get Wallets** > Use Coinbase Wallet to mcp get wallets and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app 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 Coinbase Wallet working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Coinbase Wallet app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Coinbase Wallet through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Coinbase Wallet. | 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 Coinbase Wallet actions to the runtime in a format your agent can reliably use. | 6 tools for Coinbase Wallet are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Coinbase Wallet 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 Coinbase Wallet in the browser, and the 6 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Coinbase Wallet 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 Coinbase Wallet 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 Coinbase Wallet tools Coinbase Wallet 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 Coinbase Wallet 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. ### Coinbase Wallet 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. ### OAuth finished in the browser but the account is still missing Try reconnecting Coinbase Wallet and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Hermes Agent Coinbase Wallet integration? Yes. ClawLink is the fastest way to connect Hermes to Coinbase Wallet: link your Coinbase Wallet account once in the browser and Hermes Agent can call the Coinbase Wallet API through 6 ready-made tools — no custom code or token handling. ### How do I connect Coinbase Wallet 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 Coinbase Wallet in the dashboard and Hermes can use it from the next message — no config files or API keys to manage. ### How long does it take to connect Coinbase Wallet to Hermes Agent? About two minutes. Sign in, click Connect next to Coinbase Wallet in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Coinbase Wallet up myself? The alternative to ClawLink is usually manual OAuth app 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 Coinbase Wallet working from chat. ### Hermes paired but still can't use Coinbase Wallet 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 - [Stripe](https://claw-link.dev/hermes/stripe) — Manage payments, customers, and invoices - [Hermes Zoho Books integration](https://claw-link.dev/hermes/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp](https://claw-link.dev/hermes/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts