# How to connect Realphonevalidation to Hermes Agent (paste one key, 10 tools) > Connect Realphonevalidation to Hermes with ClawLink: paste your Realphonevalidation key once and 10 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/realphonevalidation Most guides for giving Hermes Agent Realphonevalidation 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 Realphonevalidation setup: pair once in the browser and your always-on Hermes agent can act on Realphonevalidation 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 Realphonevalidation. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Realphonevalidation** — 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 realphonevalidation # connect Realphonevalidation (browser OAuth) npx -y @useclawlink/cli actions realphonevalidation # list available actions npx -y @useclawlink/cli run realphonevalidation --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 Realphonevalidation in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Realphonevalidation API key once. Verify the connection by asking Hermes: > Use Realphonevalidation to check fraud 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 Realphonevalidation is connected in the dashboard, that agent calls the same 10 Realphonevalidation 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). ## Realphonevalidation MCP for Hermes Looking for a Realphonevalidation MCP server for Hermes Agent? ClawLink connects Realphonevalidation to Hermes Agent and exposes 10 Realphonevalidation 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 Realphonevalidation integration](https://claw-link.dev/openclaw/realphonevalidation) works the same way. ## What the Hermes Agent Realphonevalidation integration can do 10 Realphonevalidation tools are ready for Hermes Agent once the account is connected. ### All 10 Realphonevalidation tools for Hermes | Tool | What it does | |---|---| | **Check fraud** `realphonevalidation_check_fraud` | Check phone number for fraud risk using Fraud Check API | | **Email verify** `realphonevalidation_email_verify` | Validate an email address and check connectivity and disposability | | **Lookup dnc** `realphonevalidation_lookup_dnc` | Check Do Not Call list status for US phone numbers | | **Rpv active** `realphonevalidation_rpv_active` | Determine if a phone number is active on a valid phone service provider | | **Rpv reassigned number lookup** `realphonevalidation_rpv_reassigned_number_lookup` | Check if a phone number has been reassigned since a given consent date | | **Rpv scrub plus** `realphonevalidation_rpv_scrub_plus` | Scrub a phone number for connection status and type | | **Rpv wireless ID** `realphonevalidation_rpv_wireless_id` | Identify whether a US phone number is landline or wireless | | **Validate phone scrub** `realphonevalidation_validate_phone_scrub` | Validate US phone numbers using budget-friendly Scrub API | | **Validate phone turbo standard** `realphonevalidation_validate_phone_turbo_standard` | Perform real-time US phone validation using Turbo Standard API | | **Validate phone turbo v3** `realphonevalidation_validate_phone_turbo_v3` | Perform comprehensive real-time phone validation using Turbo V3 API | ## Example prompts **Check Fraud** > Use Realphonevalidation to check fraud and walk me through the result in plain English. **Email Verify** > Use Realphonevalidation to email verify and walk me through the result in plain English. **Lookup Dnc** > Use Realphonevalidation to lookup dnc and walk me through the result in plain English. **Rpv Active** > Use Realphonevalidation to rpv active 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 Realphonevalidation working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Realphonevalidation API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Realphonevalidation 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 Realphonevalidation. | 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 Realphonevalidation actions to the runtime in a format your agent can reliably use. | 10 tools for Realphonevalidation are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Realphonevalidation 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 Realphonevalidation in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Realphonevalidation 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 Realphonevalidation 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 Realphonevalidation 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 Realphonevalidation tools Realphonevalidation 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 Realphonevalidation 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. ### Realphonevalidation 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 Realphonevalidation 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 Realphonevalidation integration? Yes. ClawLink is the fastest way to connect Hermes to Realphonevalidation: link your Realphonevalidation account once in the browser and Hermes Agent can call the Realphonevalidation API through 10 ready-made tools — no custom code or token handling. ### How do I connect Realphonevalidation 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 Realphonevalidation in the dashboard and Hermes can use it from the next message — no config files, and the Realphonevalidation key you paste is stored server-side instead of in your environment. ### How long does it take to connect Realphonevalidation to Hermes Agent? About two minutes. Sign in, click Connect next to Realphonevalidation in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Realphonevalidation 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 Realphonevalidation working from chat. ### Hermes paired but still can't use Realphonevalidation 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 SendGrid](https://claw-link.dev/hermes/sendgrid) — Deliver transactional and marketing emails - [Dialpad](https://claw-link.dev/hermes/dialpad) — Business phone, messaging, and video conferencing - [Discord Bot tools](https://claw-link.dev/hermes/discord-bot) — Automate Discord server actions with bot-specific permissions