The recurring question in the Hermes community -- "what is everyone actually using Hermes for?" -- deserves a structured answer. Hermes Agent has become a real choice for teams that want a self-hosted agent instead of a cloud-only framework. Here are five use cases we have seen work.
A note on versions before the list. Hermes ships every one to three days and is on the 0.20 line as of this writing. Flag names, config keys and bundled skills all move at that cadence, so this post describes the shapes of the workloads and keeps release-specific claims labelled. When a command below does not match your install, run hermes --help rather than trusting a blog post; the workload patterns outlive the flags.
Why Teams Pick Hermes Over Alternatives
Three reasons show up repeatedly, and none of them have changed across the releases: a self-hostable install (no cloud dependency), MCP-native tool support (drop any MCP server in), and config-first setup instead of Python glue. For teams that already run infrastructure, Hermes fits next to their other services without a new deployment model.
Use Case 1: Internal Research Agent
Hermes plus Scavio plus an internal document MCP produces a research agent that pulls from both sides in the same session. Run it on an internal server, expose over an HTTP endpoint, let any team query it.
# hermes.yaml -- config key names vary by release; check your version's docs
tools:
- name: scavio
type: mcp
endpoint: https://mcp.scavio.dev/mcp
headers:
x-api-key: ${SCAVIO_API_KEY}
- name: docs
type: mcp
command: ./internal-docs-mcp
system_prompt: |
You are an internal research agent.
Use scavio for external research, docs for internal context.
Cite every claim.The hosted MCP server speaks streamable HTTP and authenticates on the x-api-key header. It exposes 191 tools in total, but the default surface registers 106 of them across 11 platforms -- enough for most research agents without flooding the context window on every session. Widen it per-agent with the x-scavio-platforms header, which is additive: default,zillow,sec keeps the default set and adds two more. all registers all 191 and is a large payload in every session, so reach for it deliberately rather than by habit. Locally the same selection is available as the SCAVIO_PLATFORMS env var. Details in the MCP server docs.
Use Case 2: Coding Agent on a Private Repo
A Hermes instance pointed at a GitHub MCP and Scavio's web MCP becomes a coding agent that can search live GitHub issues, fetch doc pages, and generate code with fresh context. Hosted on the team's own infra, with the codebase never leaving the network.
This is the pattern most sensitive to tool-surface size: a coding agent already carries file, shell and VCS tools, so start from the default Scavio surface and add platforms only when a task actually needs them.
Use Case 3: Outbound Research Bot
For SDR teams, Hermes runs account-research tasks as background jobs. Given a company domain, it pulls SERP, Reddit mentions, YouTube interviews of founders, and recent news. Output goes to Airtable or HubSpot. Lower cost than Clay at scale because Hermes plus Scavio unbundles the LLM from the data.
# Run as a scheduled job. Subcommand and flag names move between releases --
# this is the shape, not a copy-paste contract. Verify with `hermes --help`.
hermes run --flow account-research --input '{"domain": "example.com"}'The YouTube leg of this flow is where teams most often hit a wall. Hermes bundles a youtube-content skill built on the free youtube-transcript-api plus yt-dlp, and it breaks repeatedly: undeclared dependencies that fail on a clean install, transcript fetches that die behind proxies, and a Shorts filter that does not filter. For a one-off lookup that is an annoyance; for a scheduled job that runs unattended overnight it is a silent data gap, because the flow completes with an empty transcript field and nobody notices until the research output is thin.
Scavio's YouTube endpoints cover the same ground as server-side calls with no local yt-dlp to keep current: POST /api/v1/youtube/search (2 credits), POST /api/v1/youtube/video (1 credit) for metadata and the captions list, and POST /api/v1/youtube/transcript (8 credits) for a plain transcript or timed subtitles. Shorts have a dedicated endpoint rather than a filter flag. Full list in the YouTube API docs.
curl -X POST https://api.scavio.dev/api/v1/youtube/transcript \
-H "Authorization: Bearer $SCAVIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"video_id": "VIDEO_ID_HERE", "format": "text"}'Use Case 4: Customer Support Triage
Hermes ingests incoming support tickets, uses Scavio to search the public web and the internal knowledge base, proposes a draft answer, and escalates when confidence is low. Because it runs on-prem, support data never leaves the infrastructure.
Use Case 5: Compliance Monitoring
Hermes runs daily checks on regulated terms across public filings and Reddit. When a trigger is detected, alert via Slack. The deterministic config-driven flow and self-hosted deployment matter for compliance teams that cannot run this on a third-party cloud. SEC EDGAR and UK Companies House are both first-class platforms, so filings and officer records come back as JSON rather than as scraped HTML you have to keep parsing.
Installing Scavio Inside Hermes
Beyond the MCP server, Scavio publishes skills to ClawHub, which Hermes installs directly:
hermes skills install @scavio-ai/scavio-amazonThere are 50 skills covering the 50 platforms, including the generic Extract endpoint (any URL to markdown, text or HTML). Skills are the lighter option when an agent only needs one or two platforms: you get the trigger conditions, parameter tables and failure handling for that platform without registering the full tool surface. The MCP server is the better option when one agent needs to reach across many platforms in a single session. See the ClawHub docs for the full skill list.
What Does Not Work Well
Hermes is weaker than LangChain for rapid prototyping of new flows (Python iteration speed) and weaker than a polished desktop client for interactive end-user chat. Pick Hermes when the agent is a service, not an app.
The other honest caveat is churn. A project shipping every one to three days will occasionally break a bundled skill or rename a flag in a minor release. Pin your Hermes version in production, read the changelog before bumping, and keep the external data layer behind a stable HTTP contract so an agent upgrade cannot take your data pipeline down with it.
Setup
Install Hermes, drop a config file, add Scavio as an MCP tool, run. Most teams have a working agent on day one. The how-to-give-hermes-agent-web-search-access tutorial has the exact config.
New accounts get 50 Scavio credits on signup, one time, no card required -- enough to prove the flow end to end before you decide anything. Get a key.
The Cost Math
Credit cost varies by platform, so do the arithmetic against the endpoints your flow actually calls rather than against a flat per-request number. Google, Amazon, Walmart, eBay, Target, Airbnb, Zillow, Redfin, SEC EDGAR, Companies House and Meta Ads are 1 credit. Threads, Yelp, Tripadvisor, Indeed, Capterra, Google Play and Home Depot are 2. G2 is 5. Kuaishou ranges from 1 to 40 depending on the endpoint. YouTube search is 2 and a transcript is 8. Every response carries credits_used and credits_remaining, so an agent can meter itself.
Worked example: an account-research flow doing one SERP call, one Reddit call and one YouTube transcript per account costs 1 + 1 + 8 = 10 credits per account. At 50 accounts a day that is 500 credits a day, roughly 15,000 a month -- above the $30 Project plan's 7,000 credits, so the $100 Bootstrap plan at 28,000 credits is the honest fit. Drop the transcript and the same 50 accounts a day fit inside the $30 plan with room to spare.
The structural point holds either way: hosted Clay-like platforms charge for the enrichment and the storage and the schema as one bundle. Hermes plus Scavio unbundles the LLM from the data, so you pay for the calls you make and keep the output in your own schema. For teams that own their ops, that is the trade worth making.