# How to connect Extracta.ai to Hermes Agent (paste one key, 10 tools) > Connect Extracta.ai to Hermes with ClawLink: paste your Extracta.ai 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/extracta-ai Most guides for giving Hermes Agent Extracta.ai 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 Extracta.ai setup: pair once in the browser and your always-on Hermes agent can act on Extracta.ai 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 Extracta.ai. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Extracta.ai** — 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 extracta-ai # connect Extracta.ai (browser OAuth) npx -y @useclawlink/cli actions extracta-ai # list available actions npx -y @useclawlink/cli run extracta-ai --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 Extracta.ai in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Extracta.ai API key once. Verify the connection by asking Hermes: > Pull the relevant data from Extracta.ai, 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 Extracta.ai is connected in the dashboard, that agent calls the same 10 Extracta.ai 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). ## Extracta.ai MCP for Hermes Looking for a Extracta.ai MCP server for Hermes Agent? ClawLink connects Extracta.ai to Hermes Agent and exposes 10 Extracta.ai 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 Extracta.ai integration](https://claw-link.dev/openclaw/extracta-ai) works the same way. ## What the Hermes Agent Extracta.ai integration can do 10 Extracta.ai tools are ready for Hermes Agent once the account is connected. The 8 below are the ones people reach for most; your agent can call all 10. ### 8 of 10 Extracta.ai tools for Hermes | Tool | What it does | |---|---| | **Get batch results** `extracta_ai_get_batch_results` | Retrieves extraction results for a specific batch of documents | | **Get credits** `extracta_ai_get_credits` | Retrieves the current credit balance available on the account | | **View classification** `extracta_ai_view_classification` | Retrieves details of an existing classification configuration including name, description | | **View extraction** `extracta_ai_view_extraction` | Retrieves detailed configuration and status information for an existing extraction job | | **Create classification** `extracta_ai_create_classification` | Creates a new document classification configuration | | **Create extraction** `extracta_ai_create_extraction` | Creates a new extraction configuration for processing documents | | **Update classification** `extracta_ai_update_classification` | Updates an existing document classification by modifying its parameters | | **Update extraction** `extracta_ai_update_extraction` | Updates an existing document extraction process by modifying specified parameters | ## Example prompts **Get Batch Results** > Pull the relevant data from Extracta.ai, summarize it in plain English, and point out anything that needs attention. **Get Credits** > Pull the relevant data from Extracta.ai, summarize it in plain English, and point out anything that needs attention. **View Classification** > Use Extracta.ai to view classification and walk me through the result in plain English. **View Extraction** > Use Extracta.ai to view extraction 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 Extracta.ai working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Extracta.ai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Extracta.ai 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 Extracta.ai. | 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 Extracta.ai actions to the runtime in a format your agent can reliably use. | 10 tools for Extracta.ai are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Extracta.ai 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 Extracta.ai in the browser, and the 10 tools above work from chat. There is no SDK and no config file, and the Extracta.ai 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 Extracta.ai 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 Extracta.ai 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 Extracta.ai tools Extracta.ai 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 Extracta.ai 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. ### Extracta.ai 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 Extracta.ai 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 Extracta.ai integration? Yes. ClawLink is the fastest way to connect Hermes to Extracta.ai: link your Extracta.ai account once in the browser and Hermes Agent can call the Extracta.ai API through 10 ready-made tools — no custom code or token handling. ### How do I connect Extracta.ai 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 Extracta.ai in the dashboard and Hermes can use it from the next message — no config files, and the Extracta.ai key you paste is stored server-side instead of in your environment. ### How long does it take to connect Extracta.ai to Hermes Agent? About two minutes. Sign in, click Connect next to Extracta.ai in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Extracta.ai 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 Extracta.ai working from chat. ### Hermes paired but still can't use Extracta.ai 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 DataRobot integration](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Chatbotkit tools](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Hermes Just One API integration](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.