# How to connect Addressfinder to Hermes Agent (paste one key, 17 tools) > Connect Addressfinder to Hermes with ClawLink: paste your Addressfinder key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/addressfinder Most guides for giving Hermes Agent Addressfinder 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 Addressfinder setup: pair once in the browser and your always-on Hermes agent can act on Addressfinder 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 Addressfinder. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Addressfinder** — 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 addressfinder # connect Addressfinder (browser OAuth) npx -y @useclawlink/cli actions addressfinder # list available actions npx -y @useclawlink/cli run addressfinder --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 Addressfinder in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Addressfinder API key once. Verify the connection by asking Hermes: > Use Addressfinder to au address autocomplete api 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 Addressfinder is connected in the dashboard, that agent calls the same 17 Addressfinder 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). ## Addressfinder MCP for Hermes Looking for a Addressfinder MCP server for Hermes Agent? ClawLink connects Addressfinder to Hermes Agent and exposes 17 Addressfinder 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 Addressfinder integration](https://claw-link.dev/openclaw/addressfinder) works the same way. ## What the Hermes Agent Addressfinder integration can do 17 Addressfinder tools are ready for Hermes Agent once the account is connected. ### All 17 Addressfinder tools for Hermes | Tool | What it does | |---|---| | **Au address autocomplete API** `addressfinder_au_address_autocomplete_api` | Perform interactive search of Australian addresses from the AddressFinder database | | **Au address metadata** `addressfinder_au_address_metadata` | Retrieve full metadata for an Australian address selected from the Address Autocomplete API | | **Au address verification** `addressfinder_au_address_verification` | Verify Australian addresses against PAF/GNAF databases | | **Au location autocomplete API** `addressfinder_au_location_autocomplete_api` | Perform interactive autocomplete search for Australian streets, suburbs, and states | | **Au location metadata API** `addressfinder_au_location_metadata_api` | Retrieve comprehensive metadata for an Australian location (street, suburb, or state) selected | | **Email verification API** `addressfinder_email_verification_api` | Verify email addresses including syntax validation, domain existence, and email account | | **Int address autocomplete API** `addressfinder_int_address_autocomplete_api` | Search for international addresses using autocomplete functionality | | **Int address metadata API** `addressfinder_int_address_metadata_api` | Retrieve full metadata for an international address selected from the Address Autocomplete API | | **Nz address autocomplete** `addressfinder_nz_address_autocomplete` | Perform interactive search for New Zealand addresses | | **Nz address metadata** `addressfinder_nz_address_metadata` | Retrieve full metadata for a NZ address including coordinates, census data, and postal details | | **Nz address reverse geocode** `addressfinder_nz_address_reverse_geocode` | Reverse geocode NZ addresses from GPS coordinates | | **Nz address verification API** `addressfinder_nz_address_verification_api` | Verify New Zealand addresses against the Addressfinder database | | **Nz location autocomplete** `addressfinder_nz_location_autocomplete` | Perform interactive search for New Zealand streets, suburbs, cities, and regions | | **Nz location metadata** `addressfinder_nz_location_metadata` | Retrieve full metadata for a New Zealand location selected from the Location Autocomplete API | | **Nz poi autocomplete API** `addressfinder_nz_poi_autocomplete_api` | Perform interactive search for points of interest in New Zealand | | **Nzpoi metadata API** `addressfinder_nzpoi_metadata_api` | Retrieve comprehensive metadata for New Zealand points of interest including coordinates and | | **Phone verification API** `addressfinder_phone_verification_api` | Verify phone numbers through syntax, range checks, and network verification | ## Example prompts **Au Address Autocomplete Api** > Use Addressfinder to au address autocomplete api and walk me through the result in plain English. **Au Address Metadata** > Use Addressfinder to au address metadata and walk me through the result in plain English. **Au Address Verification** > Use Addressfinder to au address verification and walk me through the result in plain English. **Au Location Autocomplete Api** > Use Addressfinder to au location autocomplete api and walk me through the result in plain English. ## 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 Addressfinder working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Addressfinder API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Addressfinder 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 Addressfinder. | 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 Addressfinder actions to the runtime in a format your agent can reliably use. | 17 tools for Addressfinder are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Addressfinder 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 Addressfinder in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the Addressfinder 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 Addressfinder 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 Addressfinder 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 Addressfinder tools Addressfinder 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 Addressfinder 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. ### Addressfinder 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 Addressfinder 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 Addressfinder integration? Yes. ClawLink is the fastest way to connect Hermes to Addressfinder: link your Addressfinder account once in the browser and Hermes Agent can call the Addressfinder API through 17 ready-made tools — no custom code or token handling. ### How do I connect Addressfinder 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 Addressfinder in the dashboard and Hermes can use it from the next message — no config files, and the Addressfinder key you paste is stored server-side instead of in your environment. ### How long does it take to connect Addressfinder to Hermes Agent? About two minutes. Sign in, click Connect next to Addressfinder in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Addressfinder 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 Addressfinder working from chat. ### Hermes paired but still can't use Addressfinder 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 - [GitHub tools](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.