ClawLink

How to connect Exa to Hermes Agent

Connect Exa to Hermes with ClawLink: paste your Exa key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Exa
Exa
ExaAPI KEYMCP

Exa focuses on data extraction and search, helping teams gather, analyze, and visualize information from websites, APIs, or internal databases.. Once connected, Hermes Agent can read and act on Exa from chat — pairing, token refresh, and tool wiring handled for you.

64 tools

Most guides for giving Hermes Agent Exa 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 Exa setup: pair once in the browser and your always-on Hermes agent can act on Exa 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 Exa.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Exa

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Exa?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

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 Exa in the ClawLink dashboard — paste your Exa API key once.

Verify the connection by asking Hermes:

Pull the relevant data from Exa, 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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Exa is connected in the dashboard, that agent calls the same 64 Exa tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Exa MCP for Hermes

Looking for a Exa MCP server for Hermes Agent? ClawLink connects Exa to Hermes Agent and exposes 64 Exa tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Exa integration works the same way.

What the Hermes Agent Exa integration can do

64 Exa 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 64.

30 of 64 Exa tools for Hermes

ToolWhat it does
Get agent run exa_get_agent_runRetrieve an Agent run to inspect its status, output, citations, usage, or cost
Get API key exa_get_api_keyRetrieve details of a specific API key by its ID
Get API key usage exa_get_api_key_usageGet an Exa API key's total cost and cost breakdown for a time period
Get event exa_get_eventGet details of a specific event by its ID
Get import exa_get_importRetrieve an import by ID to inspect its status, entity count, and failure details
Get search monitor exa_get_search_monitorRetrieve a Search API monitor's configuration, status, and next scheduled run by ID
Get search monitor run exa_get_search_monitor_runRetrieve a Search API monitor run's status and full output when completed
Get webhook exa_get_webhookRetrieve a webhook's status, events, destination URL, and metadata by ID
Get webset exa_get_websetRetrieve a Webset by ID or external ID, including its status and operations
Get webset enrichment exa_get_webset_enrichmentRetrieve an enrichment configured on a Webset, including its status, description, format, and
Get webset item exa_get_webset_itemRetrieve a Webset item by ID, including its properties, evaluations, and enrichments
Get webset search exa_get_webset_searchRetrieve a Webset search by ID to inspect its status, progress, and recall metrics
Get websets monitor exa_get_websets_monitorRetrieve a Websets monitor's status, schedule, search behavior, and last run
Get websets monitor run exa_get_websets_monitor_runRetrieve a Websets monitor run's status, type, timestamps, and failure reason
Get websets team info exa_get_websets_team_infoGet the authenticated Websets team's identity, current concurrency usage, and limits
List agent run events exa_list_agent_run_eventsList one page of stored Exa Agent run events as JSON, with cursor pagination
List agent runs exa_list_agent_runsList one page of your team's Exa Agent runs, ordered newest to oldest
List API keys exa_list_api_keysList the authenticated Exa team's API keys, or retrieve one by API key ID
List events exa_list_eventsList all events that have occurred in the system
List imports exa_list_importsList Websets imports with cursor-based pagination to inspect import jobs
List search monitor runs exa_list_search_monitor_runsList one page of a Search API monitor's runs, newest first, including status and output
List search monitors exa_list_search_monitorsList one page of the authenticated team's Search API monitors, not Websets monitors
List webhook attempts exa_list_webhook_attemptsList one page of a webhook's delivery attempts in descending order
List webhooks exa_list_webhooksList all webhooks for Websets
List webset items exa_list_webset_itemsList one page of a Webset's items, optionally filtered by source ID
List websets exa_list_websetsList one page of Websets, optionally filtered by ID, external ID, or title
List websets monitor runs exa_list_websets_monitor_runsList one page of runs for a Websets monitor, including status and timestamps
List websets monitors exa_list_websets_monitorsList one page of Websets monitors, optionally filtered by Webset ID
Preview webset exa_preview_websetPreview how Exa interprets a search before creating a Webset
Answer exa_answerGenerates a direct, citation-backed answer to a clear natural language question or topic using

Try it: find the Exa tool you need

Browse the 30 Exa tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Exa, summarize it in plain English, and point out anything that needs attention.

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 Exa working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Exa API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Exa account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Exa.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Exa actions to the runtime in a format your agent can reliably use.64 tools for Exa are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Exa 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 Exa in the browser, and the 64 tools above work from chat. There is no SDK and no config file, and the Exa key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use Exa

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 Exa 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 Exa tools

Exa 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 Exa 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.

Exa 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 Exa has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Hermes Agent Exa integration?

Yes. ClawLink is the fastest way to connect Hermes to Exa: link your Exa account once in the browser and Hermes Agent can call the Exa API through 64 ready-made tools — no custom code or token handling.

How do I connect Exa 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 Exa in the dashboard and Hermes can use it from the next message — no config files, and the Exa key you paste is stored server-side instead of in your environment.

How long does it take to connect Exa to Hermes Agent?

About two minutes. Sign in, click Connect next to Exa in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Exa 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 Exa working from chat.

Hermes paired but still can't use Exa

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.

On this page