# How to connect RedCircle API to Hermes Agent (paste one key, 32 tools) > Connect RedCircle API to Hermes with ClawLink: paste your RedCircle API key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/redcircle-api Most guides for giving Hermes Agent RedCircle API 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 RedCircle API setup: pair once in the browser and your always-on Hermes agent can act on RedCircle API 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 RedCircle API. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect RedCircle API** — 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 redcircle-api # connect RedCircle API (browser OAuth) npx -y @useclawlink/cli actions redcircle-api # list available actions npx -y @useclawlink/cli run redcircle-api --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 RedCircle API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your RedCircle API API key once. Verify the connection by asking Hermes: > Pull the relevant data from RedCircle API, summarize it in plain English, and point out anything that needs attention. ### 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 RedCircle API is connected in the dashboard, that agent calls the same 32 RedCircle API 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). ## RedCircle API MCP for Hermes Looking for a RedCircle API MCP server for Hermes Agent? ClawLink connects RedCircle API to Hermes Agent and exposes 32 RedCircle API 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 RedCircle API integration](https://claw-link.dev/openclaw/redcircle-api) works the same way. ## What the Hermes Agent RedCircle API integration can do 32 RedCircle API tools are ready for Hermes Agent once the account is connected. The 27 below are the ones people reach for most; your agent can call all 32. ### 27 of 32 RedCircle API tools for Hermes | Tool | What it does | |---|---| | **Get account** `redcircle_api_get_account` | Retrieve account information, usage metrics, and platform status | | **Get collection** `redcircle_api_get_collection` | Retrieve complete information about a specific collection | | **Get requests CSV links** `redcircle_api_get_requests_csv_links` | Retrieve CSV download links for all requests in a collection | | **Get requests json links** `redcircle_api_get_requests_json_links` | Retrieve download links for all requests in a collection in JSON format | | **Get result set CSV** `redcircle_api_get_result_set_csv` | Retrieve a result set in CSV format with optional field filtering | | **Get result set json** `redcircle_api_get_result_set_json` | Retrieve a result set in JSON format with download links | | **Get result set jsonlines** `redcircle_api_get_result_set_jsonlines` | Retrieve a result set in JSON Lines format with download links | | **Get target product data** `redcircle_api_get_target_product_data` | Retrieve Target data in real-time including search results, product information, reviews, or | | **List categories** `redcircle_api_list_categories` | Retrieve all top-level (root) categories or filter results using optional parameters | | **List collections** `redcircle_api_list_collections` | Retrieve all collections configured on your RedCircle API account with filtering and pagination | | **List destinations** `redcircle_api_list_destinations` | Retrieve all destinations configured on your RedCircle API account with pagination and filtering | | **List error logs** `redcircle_api_list_error_logs` | List all error logs on your RedCircle API account | | **List requests by page** `redcircle_api_list_requests_by_page` | Retrieve requests for a collection in paginated format | | **List result sets** `redcircle_api_list_result_sets` | List all result sets for a collection | | **List zipcodes** `redcircle_api_list_zipcodes` | Retrieve all zipcodes associated with your account with optional filtering | | **Add zipcodes** `redcircle_api_add_zipcodes` | Add zipcodes to your RedCircle API account for geolocation targeting | | **Create collection** `redcircle_api_create_collection` | Create a new collection for running up to 15,000 requests on a schedule | | **Create destination** `redcircle_api_create_destination` | Create a new destination for uploading Collection Result Sets to cloud storage | | **Create requests** `redcircle_api_create_requests` | Add up to 1,000 requests to an existing collection | | **Resend webhook** `redcircle_api_resend_webhook` | Resend a previously configured webhook POST request for a result set | | **Start collection** `redcircle_api_start_collection` | Initiate execution of a RedCircle API collection | | **Update collection** `redcircle_api_update_collection` | Update an existing collection's configuration and settings | | **Update destination** `redcircle_api_update_destination` | Modify an existing destination configuration on your RedCircle API account | | **Update request** `redcircle_api_update_request` | Modify a request within a collection | | **Clear collection requests** `redcircle_api_clear_collection_requests` | Remove all requests from a specified collection | | **Stop all collections** `redcircle_api_stop_all_collections` | Halt all currently active collections on your account | | **Stop collection** `redcircle_api_stop_collection` | Halt an active collection in queued or running state | ## Example prompts **Get Account** > Pull the relevant data from RedCircle API, summarize it in plain English, and point out anything that needs attention. **Get Collection** > Pull the relevant data from RedCircle API, summarize it in plain English, and point out anything that needs attention. **Get Requests Csv Links** > Pull the relevant data from RedCircle API, summarize it in plain English, and point out anything that needs attention. **Get Requests Json Links** > Pull the relevant data from RedCircle API, 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 RedCircle API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the RedCircle API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected RedCircle API 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 RedCircle API. | 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 RedCircle API actions to the runtime in a format your agent can reliably use. | 32 tools for RedCircle API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes RedCircle API 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 RedCircle API in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the RedCircle API 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 RedCircle API 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 RedCircle API 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 RedCircle API tools RedCircle API 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 RedCircle API 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. ### RedCircle API 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 RedCircle API 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 RedCircle API integration? Yes. ClawLink is the fastest way to connect Hermes to RedCircle API: link your RedCircle API account once in the browser and Hermes Agent can call the RedCircle API API through 32 ready-made tools — no custom code or token handling. ### How do I connect RedCircle API 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 RedCircle API in the dashboard and Hermes can use it from the next message — no config files, and the RedCircle API key you paste is stored server-side instead of in your environment. ### How long does it take to connect RedCircle API to Hermes Agent? About two minutes. Sign in, click Connect next to RedCircle API in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring RedCircle API 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 RedCircle API working from chat. ### Hermes paired but still can't use RedCircle API 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 - [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](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.