# How to connect Nutrient Document Web Services API to Hermes Agent (paste one key, 11 tools)

> Connect Nutrient Document Web Services API to Hermes with ClawLink: paste your Nutrient Document Web Services API key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/nutrient-document-web-services-api

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

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Nutrient Document Web Services 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 nutrient-document-web-services-api  # connect Nutrient Document Web Services API (browser OAuth)
npx -y @useclawlink/cli actions nutrient-document-web-services-api  # list available actions
npx -y @useclawlink/cli run nutrient-document-web-services-api <action> --input '<json>'  # 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 Nutrient Document Web Services API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Nutrient Document Web Services API API key once.

Verify the connection by asking Hermes:

> Use Nutrient Document Web Services API to analyze build cost 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 Nutrient Document Web Services API is connected in the dashboard, that agent calls the same 11 Nutrient Document Web Services 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).

## Nutrient Document Web Services API MCP for Hermes

Looking for a Nutrient Document Web Services API MCP server for Hermes Agent? ClawLink connects Nutrient Document Web Services API to Hermes Agent and exposes 11 Nutrient Document Web Services 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 Nutrient Document Web Services API integration](https://claw-link.dev/openclaw/nutrient-document-web-services-api) works the same way.

## What the Hermes Agent Nutrient Document Web Services API integration can do

11 Nutrient Document Web Services API tools are ready for Hermes Agent once the account is connected.

### All 11 Nutrient Document Web Services API tools for Hermes

| Tool | What it does |
|---|---|
| **Analyze build cost** `nutrient_document_web_services_api_analyze_build_cost` | Estimate the credits and Processor features required by Build API instructions without |
| **Get account info** `nutrient_document_web_services_api_get_account_info` | Return the connected Nutrient account's subscription type, status, and estimated remaining |
| **Get processor usage** `nutrient_document_web_services_api_get_processor_usage` | Return the connected account's Processor subscription status and credit usage counters |
| **Build document** `nutrient_document_web_services_api_build_document` | Synchronously create one document from remote files, remote HTML, new pages, and composable |
| **Convert markdown to PDF** `nutrient_document_web_services_api_convert_markdown_to_pdf` | Convert CommonMark or GitHub-Flavored Markdown text into a PDF using optional built-in styling |
| **Create PDF from web page** `nutrient_document_web_services_api_create_pdf_from_web_page` | Render an HTML web page at a public URL, with optional page layout settings, into a PDF |
| **Make PDF accessible** `nutrient_document_web_services_api_make_pdf_accessible` | Auto-tag a PDF at a remote URL for PDF/UA screen-reader accessibility and return the result's |
| **Ocr PDF** `nutrient_document_web_services_api_ocr_pdf` | Apply optical character recognition to a PDF at a remote URL and return a searchable PDF's |
| **Stage PDF redactions** `nutrient_document_web_services_api_stage_pdf_redactions` | Find matching content in a remote PDF and return a review PDF's filename, media type, and |
| **Watermark PDF** `nutrient_document_web_services_api_watermark_pdf` | Add a positioned text or image watermark to every page of a PDF at a public URL and return the |
| **Revoke jwt token** `nutrient_document_web_services_api_revoke_jwt_token` | Immediately revoke a bearer token created by CREATE_JWT_TOKEN using its ID |

## Example prompts

**Analyze Build Cost**

> Use Nutrient Document Web Services API to analyze build cost and walk me through the result in plain English.

**Get Account Info**

> Pull the relevant data from Nutrient Document Web Services API, summarize it in plain English, and point out anything that needs attention.

**Get Processor Usage**

> Pull the relevant data from Nutrient Document Web Services API, summarize it in plain English, and point out anything that needs attention.

**Build Document**

> Use Nutrient Document Web Services API to build document 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 Nutrient Document Web Services API working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Nutrient Document Web Services API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Nutrient Document Web Services 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 Nutrient Document Web Services 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 Nutrient Document Web Services API actions to the runtime in a format your agent can reliably use. | 11 tools for Nutrient Document Web Services API are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Nutrient Document Web Services 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 Nutrient Document Web Services API in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Nutrient Document Web Services 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 Nutrient Document Web Services 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 Nutrient Document Web Services 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 Nutrient Document Web Services API tools
Nutrient Document Web Services 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 Nutrient Document Web Services 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.

### Nutrient Document Web Services 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 Nutrient Document Web Services 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 Nutrient Document Web Services API integration?
Yes. ClawLink is the fastest way to connect Hermes to Nutrient Document Web Services API: link your Nutrient Document Web Services API account once in the browser and Hermes Agent can call the Nutrient Document Web Services API API through 11 ready-made tools — no custom code or token handling.

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

### How long does it take to connect Nutrient Document Web Services API to Hermes Agent?
About two minutes. Sign in, click Connect next to Nutrient Document Web Services API in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

### Why use ClawLink instead of wiring Nutrient Document Web Services 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 Nutrient Document Web Services API working from chat.

### Hermes paired but still can't use Nutrient Document Web Services 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

- [Connect GitHub](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows
- [Connect PagerDuty](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect 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.
