RentAHuman for Hermes Agent
Connect Hermes to RentAHuman's MCP server to find people and manage real-world
work. The package uses the published rentahuman-mcp server and pins its npm
version so updates happen through a reviewed catalog release.
Setup
-
Install and enable the plugin from Hermes' Plugin Catalog:
hermes plugins install rentahuman --enable -
If Hermes is already running, stop its gateway so the next session starts
the RentAHuman MCP server:hermes gateway stop -
Start a new Hermes session and ask it to search for a human or service.
Search works without an account or API key. -
To post bounties, message people, or manage payments, create an API key at
https://rentahuman.ai/account/api-keys and add it to the Hermes profile
environment file (~/.hermes/.env):RENTAHUMAN_API_KEY=rah_YOUR_API_KEYRun
hermes gateway stopagain so the next session passes the key to the
MCP server, then ask Hermes to check your RentAHuman account status.
The MCP server runs locally through npx; marketplace requests go to
https://rentahuman.ai/api. The API key stays in the Hermes profile and is
passed to the MCP subprocess through the environment.
Usage attribution
The plugin sets RENTAHUMAN_INTEGRATION_SOURCE=hermes_plugin for the MCP
server. The server then sends the header
X-RentAHuman-Integration-Source: hermes_plugin to rentahuman.ai on the API
requests your tool calls make. It is not sent at startup. It adds no network
destination and no credential. RentAHuman uses it to count how many accounts
use RentAHuman through Hermes, and to label bounties and service bookings
created this way through funding, completion and payment. The label is
self-reported: it is not identity and grants no access. It never changes which
account is used, what you can do, or what you pay. The attribution data does
not include your prompts, tool arguments or results, IP address, or user agent.
To opt out, delete that env entry from the installed plugin's mcp.json.
Use either this plugin or the hermes mcp install rentahuman remote server in
a profile, not both. Both register a server named rentahuman, and Hermes
skips this plugin's server when the other is configured.
Approval and payment behavior
The plugin marks the MCP server as untrusted. Hermes asks for approval before
each tool call that can change state, send a message, accept a worker, or move
money, including a create_bounty preview with dryRun: true. Read-only search
and status calls do not require approval. Review each requested action and its
amount before approving it.
For a new bounty, inspect the create_bounty dry-run preview and confirm the
budget and task terms before creating or funding it. Review worker submissions
and evidence before approving work or releasing payment.
See the RentAHuman MCP guide for the complete
tool catalog and workflow documentation.
README from the reviewed commit dc4a731; it updates when the author re-pins.

RentAHuman