# How to connect Rev AI to Hermes Agent (paste one key, 36 tools)

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

Web version: https://claw-link.dev/hermes/rev

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

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Rev 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 rev  # connect Rev AI (browser OAuth)
npx -y @useclawlink/cli actions rev  # list available actions
npx -y @useclawlink/cli run rev <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 Rev AI in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Rev AI API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Rev 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 Rev AI is connected in the dashboard, that agent calls the same 36 Rev 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).

## Rev AI MCP for Hermes

Looking for a Rev AI MCP server for Hermes Agent? ClawLink connects Rev AI to Hermes Agent and exposes 36 Rev 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 Rev AI integration](https://claw-link.dev/openclaw/rev) works the same way.

## What the Hermes Agent Rev AI integration can do

36 Rev AI 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 36.

### 30 of 36 Rev AI tools for Hermes

| Tool | What it does |
|---|---|
| **Get account** `rev_get_account` | Retrieves Rev AI account information including email, credit balance (in hours), and HIPAA |
| **Get alignment job** `rev_get_alignment_job` | Get details of a specific forced alignment job including its status |
| **Get alignment transcript** `rev_get_alignment_transcript` | Retrieve the aligned transcript with timestamps for a completed alignment job |
| **Get captions** `rev_get_captions` | Retrieve captions (SRT or VTT) for a completed Rev.ai transcription job |
| **Get captions translation** `rev_get_captions_translation` | Retrieve translated captions for a completed Rev.ai transcription job |
| **Get custom vocabulary details** `rev_get_custom_vocabulary_details` | Retrieve custom vocabulary processing details |
| **Get job by ID** `rev_get_job_by_id` | Fetch details of a transcription job by its ID |
| **Get language ID job** `rev_get_language_id_job` | Fetch details of a language identification job by its ID |
| **Get language ID result** `rev_get_language_id_result` | Retrieve language identification results for a completed job |
| **Get list of jobs** `rev_get_list_of_jobs` | Retrieves a list of transcription jobs from the past 30 days in reverse chronological order |
| **Get sentiment job** `rev_get_sentiment_job` | Fetch details of a sentiment analysis job by its ID |
| **Get sentiment result** `rev_get_sentiment_result` | Retrieve sentiment analysis results for a completed Rev.ai sentiment job |
| **Get topic extraction result** `rev_get_topic_extraction_result` | Retrieve topic extraction results for a completed job |
| **Get topic job** `rev_get_topic_job` | Fetch details of a topic extraction job by its ID |
| **Get transcript by ID** `rev_get_transcript_by_id` | Retrieve the transcript of a completed Rev.ai job |
| **Get transcript summary** `rev_get_transcript_summary` | Retrieve a summary of the transcript for a completed transcription job |
| **Get transcript translation** `rev_get_transcript_translation` | Retrieve a translated version of the transcript for a completed Rev.ai job |
| **List alignment jobs** `rev_list_alignment_jobs` | Retrieve a list of all forced alignment jobs for the account |
| **List custom vocabularies** `rev_list_custom_vocabularies` | Retrieve a list of all custom vocabularies for the account |
| **List language ID jobs** `rev_list_language_id_jobs` | Retrieve a list of language identification jobs for the account |
| **List sentiment jobs** `rev_list_sentiment_jobs` | Retrieve a list of all sentiment analysis jobs for the account |
| **List topic jobs** `rev_list_topic_jobs` | Retrieve a list of all topic extraction jobs for the account |
| **Start stream transcription** `rev_start_stream_transcription` | Start a WebSocket transcription stream |
| **Create rtmp stream** `rev_create_rtmp_stream` | Create an RTMP live stream session for real-time transcription of live audio/video streams |
| **Submit alignment job** `rev_submit_alignment_job` | Submit an audio file with existing transcript for forced alignment |
| **Submit custom vocabulary** `rev_submit_custom_vocabulary` | Submits a custom vocabulary to Rev.ai for improved speech recognition accuracy on |
| **Submit language ID job** `rev_submit_language_id_job` | Submit an audio file for language identification to detect the spoken language |
| **Submit sentiment analysis job** `rev_submit_sentiment_analysis_job` | Submit text for sentiment analysis to detect positive, negative, or neutral sentiments |
| **Submit topic extraction job** `rev_submit_topic_extraction_job` | Submit text or transcripts for topic extraction to identify key topics and themes |
| **Submit transcription job** `rev_submit_transcription_job` | Submit an audio or video file for asynchronous transcription using Rev.ai |

## Example prompts

**Get Account**

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

**Get Alignment Job**

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

**Get Alignment Transcript**

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

**Get Captions**

> Pull the relevant data from Rev AI, 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 Rev AI working from chat.

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

## ClawLink vs. Composio

Composio also exposes Rev 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 Rev AI in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the Rev 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 Rev 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 Rev 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 Rev AI tools
Rev 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 Rev 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.

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

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

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

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

### Hermes paired but still can't use Rev 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 Cloudinary integration](https://claw-link.dev/hermes/cloudinary) — Cloudinary is a cloud-based media management platform for uploading, storing, transforming, and delivering images and videos via CDN.
- [Penpot tools](https://claw-link.dev/hermes/penpot) — Open-source design and prototyping platform for collaborative design workflows.
- [Connect Canva](https://claw-link.dev/hermes/canva) — Create designs, upload assets, export content, and manage brand templates