# How to connect PostGrid Verify to Hermes Agent (paste one key, 12 tools) > Connect PostGrid Verify to Hermes with ClawLink: paste your PostGrid Verify key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/postgrid-verify Most guides for giving Hermes Agent PostGrid Verify 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 PostGrid Verify setup: pair once in the browser and your always-on Hermes agent can act on PostGrid Verify 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 PostGrid Verify. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect PostGrid Verify** — 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 postgrid-verify # connect PostGrid Verify (browser OAuth) npx -y @useclawlink/cli actions postgrid-verify # list available actions npx -y @useclawlink/cli run postgrid-verify --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 PostGrid Verify in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PostGrid Verify API key once. Verify the connection by asking Hermes: > Use PostGrid Verify to autocomplete address 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 PostGrid Verify is connected in the dashboard, that agent calls the same 12 PostGrid Verify 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). ## PostGrid Verify MCP for Hermes Looking for a PostGrid Verify MCP server for Hermes Agent? ClawLink connects PostGrid Verify to Hermes Agent and exposes 12 PostGrid Verify 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 PostGrid Verify integration](https://claw-link.dev/openclaw/postgrid-verify) works the same way. ## What the Hermes Agent PostGrid Verify integration can do 12 PostGrid Verify tools are ready for Hermes Agent once the account is connected. ### All 12 PostGrid Verify tools for Hermes | Tool | What it does | |---|---| | **Autocomplete address** `postgrid_verify_autocomplete_address` | Autocomplete a partially specified US or Canada address | | **Autocomplete intl address** `postgrid_verify_autocomplete_intl_address` | Retrieve complete verified international address data using an ID from the preview endpoint | | **Get autocomplete previews** `postgrid_verify_get_autocomplete_previews` | Get previews of autocompleted US and Canadian addresses | | **Get intl autocomplete previews** `postgrid_verify_get_intl_autocomplete_previews` | Get previews of autocompleted international addresses | | **Get lookup info** `postgrid_verify_get_lookup_info` | Retrieve lookup usage information for your PostGrid account | | **Lookup city state from postal** `postgrid_verify_lookup_city_state_from_postal` | Lookup city and state for a given postal or ZIP code | | **Parse address** `postgrid_verify_parse_address` | Break an address apart into its components | | **Suggest addresses** `postgrid_verify_suggest_addresses` | Find addresses similar to the given address | | **Verify address** `postgrid_verify_verify_address` | Verify and standardize a US or Canadian address | | **Verify batch addresses** `postgrid_verify_verify_batch_addresses` | Verify up to 2000 US and Canada addresses in a single API call | | **Verify international address** `postgrid_verify_verify_international_address` | Verify and standardize international addresses from 245+ countries | | **Verify intl addresses batch** `postgrid_verify_verify_intl_addresses_batch` | Verify up to 2000 international addresses in a single API call | ## Example prompts **Autocomplete Address** > Use PostGrid Verify to autocomplete address and walk me through the result in plain English. **Autocomplete Intl Address** > Use PostGrid Verify to autocomplete intl address and walk me through the result in plain English. **Get Autocomplete Previews** > Pull the relevant data from PostGrid Verify, summarize it in plain English, and point out anything that needs attention. **Get Intl Autocomplete Previews** > Pull the relevant data from PostGrid Verify, 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 PostGrid Verify working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PostGrid Verify API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PostGrid Verify 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 PostGrid Verify. | 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 PostGrid Verify actions to the runtime in a format your agent can reliably use. | 12 tools for PostGrid Verify are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PostGrid Verify 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 PostGrid Verify in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the PostGrid Verify 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 PostGrid Verify 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 PostGrid Verify 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 PostGrid Verify tools PostGrid Verify 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 PostGrid Verify 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. ### PostGrid Verify 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 PostGrid Verify 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 PostGrid Verify integration? Yes. ClawLink is the fastest way to connect Hermes to PostGrid Verify: link your PostGrid Verify account once in the browser and Hermes Agent can call the PostGrid Verify API through 12 ready-made tools — no custom code or token handling. ### How do I connect PostGrid Verify 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 PostGrid Verify in the dashboard and Hermes can use it from the next message — no config files, and the PostGrid Verify key you paste is stored server-side instead of in your environment. ### How long does it take to connect PostGrid Verify to Hermes Agent? About two minutes. Sign in, click Connect next to PostGrid Verify in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring PostGrid Verify 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 PostGrid Verify working from chat. ### Hermes paired but still can't use PostGrid Verify 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](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 - [Connect 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.