# How to connect Fidel API to Hermes Agent (paste one key, 39 tools) > Connect Fidel API to Hermes with ClawLink: paste your Fidel API key once and 39 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/fidel-api Most guides for giving Hermes Agent Fidel 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 Fidel API setup: pair once in the browser and your always-on Hermes agent can act on Fidel 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 Fidel API. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Fidel 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 fidel-api # connect Fidel API (browser OAuth) npx -y @useclawlink/cli actions fidel-api # list available actions npx -y @useclawlink/cli run fidel-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 Fidel API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Fidel API API key once. Verify the connection by asking Hermes: > Pull the relevant data from Fidel 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 Fidel API is connected in the dashboard, that agent calls the same 39 Fidel 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). ## Fidel API MCP for Hermes Looking for a Fidel API MCP server for Hermes Agent? ClawLink connects Fidel API to Hermes Agent and exposes 39 Fidel 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 Fidel API integration](https://claw-link.dev/openclaw/fidel-api) works the same way. ## What the Hermes Agent Fidel API integration can do 39 Fidel API tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 39. ### 30 of 39 Fidel API tools for Hermes | Tool | What it does | |---|---| | **Get brand** `fidel_api_get_brand` | Retrieve information about a specific brand | | **Get location** `fidel_api_get_location` | Retrieve details of a specific location by its ID | | **Get mid** `fidel_api_get_mid` | Retrieve details of a specific MID (Merchant ID) | | **Get mid request** `fidel_api_get_mid_request` | Retrieve details of a specific MID request | | **Get offer** `fidel_api_get_offer` | Retrieves detailed information about a specific offer by its unique ID | | **Get program** `fidel_api_get_program` | Retrieve details of a specific program | | **Get transaction** `fidel_api_get_transaction` | Retrieve details of a specific transaction by its ID | | **Get webhook** `fidel_api_get_webhook` | Retrieve details of a specific webhook by its unique identifier | | **List brands** `fidel_api_list_brands` | Retrieves a paginated list of all brands associated with your Fidel API account | | **List cards** `fidel_api_list_cards` | List all payment cards linked to a Fidel program | | **List cards by metadata** `fidel_api_list_cards_by_metadata` | List payment cards filtered by metadata ID | | **List cards with active offer** `fidel_api_list_cards_with_active_offer` | List all payment cards that have activated a specific offer | | **List locations** `fidel_api_list_locations` | List all locations for a program | | **List locations by brand** `fidel_api_list_locations_by_brand` | List all locations for a specific brand within a program | | **List locations by offer** `fidel_api_list_locations_by_offer` | List all locations linked to a specific offer | | **List mid requests** `fidel_api_list_mid_requests` | List all MID (Merchant ID) requests for a specific program | | **List mids** `fidel_api_list_mids` | List all MIDs (Merchant IDs) for a program | | **List missing transaction requests** `fidel_api_list_missing_transaction_requests` | List all missing transaction requests for a specific program | | **List offers** `fidel_api_list_offers` | List all offers in the Fidel API | | **List program webhooks** `fidel_api_list_program_webhooks` | List all registered webhooks for a specific program | | **List programs** `fidel_api_list_programs` | List all Fidel programs in your account | | **List transactions** `fidel_api_list_transactions` | List transactions for a Fidel program with optional filtering and pagination | | **Create brand** `fidel_api_create_brand` | Create a new brand in Fidel API | | **Create brand webhook** `fidel_api_create_brand_webhook` | Create a webhook at the brand level for receiving real-time event notifications | | **Create location** `fidel_api_create_location` | Create a new location for a program in Fidel API | | **Create mid request** `fidel_api_create_mid_request` | Create a new MID (Merchant ID) request for a specific program and location | | **Create offer** `fidel_api_create_offer` | Create a new offer in Fidel API | | **Create program** `fidel_api_create_program` | Creates a new card-linked loyalty program in Fidel | | **Create program webhook** `fidel_api_create_program_webhook` | Register a new webhook for program-related events | | **Link all program locations to offer** `fidel_api_link_all_program_locations_to_offer` | Link all brand locations in a program to an offer | ## Example prompts **Get Brand** > Pull the relevant data from Fidel API, summarize it in plain English, and point out anything that needs attention. **Get Location** > Pull the relevant data from Fidel API, summarize it in plain English, and point out anything that needs attention. **Get Mid** > Pull the relevant data from Fidel API, summarize it in plain English, and point out anything that needs attention. **Get Mid Request** > Pull the relevant data from Fidel 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 Fidel API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Fidel API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Fidel 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 Fidel 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 Fidel API actions to the runtime in a format your agent can reliably use. | 39 tools for Fidel API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Fidel 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 Fidel API in the browser, and the 39 tools above work from chat. There is no SDK and no config file, and the Fidel 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 Fidel 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 Fidel 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 Fidel API tools Fidel 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 Fidel 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. ### Fidel 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 Fidel 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 Fidel API integration? Yes. ClawLink is the fastest way to connect Hermes to Fidel API: link your Fidel API account once in the browser and Hermes Agent can call the Fidel API API through 39 ready-made tools — no custom code or token handling. ### How do I connect Fidel 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 Fidel API in the dashboard and Hermes can use it from the next message — no config files, and the Fidel API key you paste is stored server-side instead of in your environment. ### How long does it take to connect Fidel API to Hermes Agent? About two minutes. Sign in, click Connect next to Fidel API in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Fidel 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 Fidel API working from chat. ### Hermes paired but still can't use Fidel 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 - [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 - [Hermes SafetyCulture integration](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.