# How to connect Eagle doc to Hermes Agent (paste one key, 9 tools) > Connect Eagle doc to Hermes with ClawLink: paste your Eagle doc key once and 9 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/eagle-doc Most guides for giving Hermes Agent Eagle doc 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 Eagle doc setup: pair once in the browser and your always-on Hermes agent can act on Eagle doc 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 Eagle doc. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Eagle doc** — 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 eagle-doc # connect Eagle doc (browser OAuth) npx -y @useclawlink/cli actions eagle-doc # list available actions npx -y @useclawlink/cli run eagle-doc --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 Eagle doc in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Eagle doc API key once. Verify the connection by asking Hermes: > Use Eagle doc to any doc ocr 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 Eagle doc is connected in the dashboard, that agent calls the same 9 Eagle doc 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). ## Eagle doc MCP for Hermes Looking for a Eagle doc MCP server for Hermes Agent? ClawLink connects Eagle doc to Hermes Agent and exposes 9 Eagle doc 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 Eagle doc integration](https://claw-link.dev/openclaw/eagle-doc) works the same way. ## What the Hermes Agent Eagle doc integration can do 9 Eagle doc 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 9. ### 8 of 9 Eagle doc tools for Hermes | Tool | What it does | |---|---| | **Any doc ocr** `eagle_doc_any_doc_ocr` | Process any document type with OCR and automatic classification | | **Invoice ocr base64** `eagle_doc_invoice_ocr_base64` | Extract invoice data from base64 encoded images using Eagle Doc OCR API | | **Management quota** `eagle_doc_management_quota` | Get contractual quota allowance and current usage counters for all workloads | | **Receipt ocr v3** `eagle_doc_receipt_ocr_v3` | Process receipt images into structured JSON with 40+ fields including merchant info, line | | **Usage current month** `eagle_doc_usage_current_month` | Get current month's usage statistics including quota, pages processed, over-usage, and costs | | **Usage monthly history** `eagle_doc_usage_monthly_history` | Retrieve historical monthly usage data with pricing context for reconciliation and forecasting | | **Usage request logs** `eagle_doc_usage_request_logs` | Retrieve chronological list of recent API calls with page counts and timestamps | | **Batch any doc ocr** `eagle_doc_batch_any_doc_ocr` | Submit batch OCR processing tasks for various document types including bank statements | ## Example prompts **Any Doc Ocr** > Use Eagle doc to any doc ocr and walk me through the result in plain English. **Invoice Ocr Base64** > Use Eagle doc to invoice ocr base64 and walk me through the result in plain English. **Management Quota** > Use Eagle doc to management quota and walk me through the result in plain English. **Receipt Ocr V3** > Use Eagle doc to receipt ocr v3 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 Eagle doc working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Eagle doc API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Eagle doc 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 Eagle doc. | 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 Eagle doc actions to the runtime in a format your agent can reliably use. | 9 tools for Eagle doc are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Eagle doc 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 Eagle doc in the browser, and the 9 tools above work from chat. There is no SDK and no config file, and the Eagle doc 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 Eagle doc 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 Eagle doc 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 Eagle doc tools Eagle doc 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 Eagle doc 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. ### Eagle doc 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 Eagle doc 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 Eagle doc integration? Yes. ClawLink is the fastest way to connect Hermes to Eagle doc: link your Eagle doc account once in the browser and Hermes Agent can call the Eagle doc API through 9 ready-made tools — no custom code or token handling. ### How do I connect Eagle doc 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 Eagle doc in the dashboard and Hermes can use it from the next message — no config files, and the Eagle doc key you paste is stored server-side instead of in your environment. ### How long does it take to connect Eagle doc to Hermes Agent? About two minutes. Sign in, click Connect next to Eagle doc in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Eagle doc 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 Eagle doc working from chat. ### Hermes paired but still can't use Eagle doc 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 - [DataRobot tools](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.