All plugins

Certified

tinyfish

TinyFish: the web, built into Hermes. Free Search and Fetch power Hermes's own web_search and web_extract, and when a site needs clicks, forms or a login, a remote browser and the tinyfish_agent web agent handle it, signed in through saved TinyFish profiles when needed. Disclosure — sends search queries, URLs to fetch and tinyfish_agent goals with your TINYFISH_API_KEY to the TinyFish API (*.tinyfish.ai). Browser sessions and tinyfish_agent runs spend TinyFish credits. Under the default request policy each one goes through Hermes's approval prompt first (a session/always answer covers every later call; cron and unattended runs are denied unless you allow them). Setting tinyfish.credit_policy.<feature>: allow or YOLO skips the prompt. hermes tinyfish setup / browser enable (run by you) save the key to Hermes .env, set web.search_backend/extract_backend and browser.cloud_provider in config.yaml, enable the web/browser toolsets, and can install the agent-browser CLI after asking. Profile tools manage TinyFish Browser Context Profiles (saved website sign-ins) over the same API; you sign in to sites yourself at an agent.tinyfish.ai link and never give Hermes a password; the agent can create, rename and re-default profiles without asking, and deleting a profile goes through Hermes's approval prompt for each profile unless approvals are off (YOLO). Setup telemetry is off by default: only if you opt in (hermes tinyfish setup --share-usage, tinyfish.telemetry: true, or answering yes to setup's y/N question) does each setup run send one event to agent.tinyfish.ai with its outcome, where the key came from, the plugin version and OS, plus a one-way hash of the key (never the key). TINYFISH_NO_TELEMETRY=1 turns it off regardless.

tinyfish-io50Webv0.2.5Updated 11 days ago

About

TinyFish: the web, built into Hermes. Free Search and Fetch power Hermes's own web_search and web_extract, and when a site needs clicks, forms or a login, a remote browser and the tinyfish_agent web agent handle it, signed in through saved TinyFish profiles when needed. Disclosure — sends search queries, URLs to fetch and tinyfish_agent goals with your TINYFISH_API_KEY to the TinyFish API (*.tinyfish.ai). Browser sessions and tinyfish_agent runs spend TinyFish credits. Under the default request policy each one goes through Hermes's approval prompt first (a session/always answer covers every later call; cron and unattended runs are denied unless you allow them). Setting tinyfish.credit_policy.<feature>: allow or YOLO skips the prompt. hermes tinyfish setup / browser enable (run by you) save the key to Hermes .env, set web.search_backend/extract_backend and browser.cloud_provider in config.yaml, enable the web/browser toolsets, and can install the agent-browser CLI after asking. Profile tools manage TinyFish Browser Context Profiles (saved website sign-ins) over the same API; you sign in to sites yourself at an agent.tinyfish.ai link and never give Hermes a password; the agent can create, rename and re-default profiles without asking, and deleting a profile goes through Hermes's approval prompt for each profile unless approvals are off (YOLO). Setup telemetry is off by default: only if you opt in (hermes tinyfish setup --share-usage, tinyfish.telemetry: true, or answering yes to setup's y/N question) does each setup run send one event to agent.tinyfish.ai with its outcome, where the key came from, the plugin version and OS, plus a one-way hash of the key (never the key). TINYFISH_NO_TELEMETRY=1 turns it off regardless.

TinyFish for Hermes Agent

tinyfish-hermes is the first-party TinyFish plugin for Hermes Agent. It gives Hermes:

CapabilityHow
Search, Fetch (free)tinyfish web provider behind Hermes' web_search / web_extract
Browser (credits)tinyfish cloud browser provider behind Hermes' browser tools
Agent (credits)tinyfish_agent tool: goal-based automation on a real site
Profiles (free)tinyfish_*_profile(s) tools: saved website sign-ins that tinyfish_agent runs with

Install

Install from the Hermes plugin catalog, then add your key and route web tools to TinyFish:

hermes plugins install tinyfish --enable
hermes tinyfish setup

Or let the TinyFish CLI do both: it installs the same catalog plugin, seeds the API key, and points Hermes' web backends at it:

npx @tiny-fish/cli connect hermes

Authentication

The plugin authenticates with a TinyFish API key — create one at agent.tinyfish.ai/api-keys. hermes plugins install and hermes tinyfish setup both prompt for it (hidden input); setup also verifies it with one free search. Keys are resolved in order:

Env varSource
TINYFISH_API_KEYSet it yourself (shell env, or hermes tinyfish setup --api-key)
MCP_TINYFISH_API_KEYSeeded by the TinyFish npm CLI during npx @tiny-fish/cli connect hermes

CLI

The plugin registers a hermes tinyfish command and an in-session /tinyfish-status [live] command:

SubcommandPurpose
setup [--yes] [--api-key KEY] [--no-web-backend] [--live]Route web tools to TinyFish and save the API key
status [--json]Non-secret configuration status
doctor [--json] [--live] [--live-paid]Diagnostics; --live runs one real search+fetch, --live-paid a browser session per credit policy
credits {status,set,reset}Inspect or change tinyfish.credit_policy.{browser,agent}
browser {enable,disable,status}Toggle browser.cloud_provider: tinyfish
usage [--json]Wallet balance, auto-reload, and billing rates

Configuration

hermes tinyfish setup routes Hermes' web tools to TinyFish; the equivalent Hermes configuration is:

web:
  search_backend: tinyfish
  extract_backend: tinyfish

Optional request tuning under a tinyfish section:

tinyfish:
  search:
    location: US          # also: language, recency_minutes, after_date,
    domain_type: news     # before_date, page, purpose
  fetch:
    ttl: 300              # also: per_url_timeout_ms (default 90000), links, image_links

Browser sessions

Setting browser.cloud_provider: tinyfish routes Hermes' browser tools — the default Browser Use browser_exec, or the built-in browser_* tools with browser.backend: off — through TinyFish remote browser sessions. Sessions consume TinyFish credits, so they are policy-gated via tinyfish.credit_policy.browser; tinyfish_agent runs use tinyfish.credit_policy.agent:

PolicyBehavior
request (default)Opening a session (or starting an agent run) goes through Hermes' approval gate; answer [s]ession to approve the rest of the session
allowNo approval prompt
denyBlocked

One-shot hermes chat -q runs skip Hermes' own browser cleanup at exit, so the plugin closes any TinyFish sessions still open when they finish.

browser:
  cloud_provider: tinyfish
tinyfish:
  credit_policy:
    browser: request
  browser:
    timeout_seconds: 300  # optional session timeout

Browser Context Profiles

A Browser Context Profile is a saved website sign-in. It is unrelated to Hermes profiles and to tinyfish_agent's browser_profile (lite/stealth).

ToolDoes
tinyfish_list_profilesLists profiles with their signed_in_sites
tinyfish_create_profileCreates a profile and returns setup_url, where the user signs in and clicks Save profile
tinyfish_profile_sign_inReturns setup_url to add or refresh a site on an existing profile
tinyfish_update_profileRenames a profile, makes it the default, or sets its proxy country (none removes it)
tinyfish_delete_profileDeletes a profile; asks for approval first unless Hermes approvals are off (--yolo)

tinyfish_agent runs signed in with profile_id (or use_profile: true for the default profile). A profile's proxy country (set on create or update) is used for both sign-in and runs, and overrides the run's proxy_country_code. If a site blocks the sign-in page, set one and reopen the same link. setup_url asks the user to sign in to TinyFish first if that browser isn't already. Nothing bills until the user opens it; runs bill under tinyfish.credit_policy.agent.

Tool-routing guidance

When the tinyfish MCP server is also configured in Hermes (mcp_servers.tinyfish.url: https://agent.tinyfish.ai/mcp), the plugin injects once-per-context guidance steering the model between the generic web tools and the native MCP tools. Disable with tinyfish.routing_context: false.

Telemetry

Off unless you turn it on. When you opt in, each hermes tinyfish setup run sends TinyFish one event, whether it succeeds or fails: the outcome (for example completed or key_rejected), where the key came from (flag, prompt, env or none), the plugin version and OS. It sends a one-way hash of the API key, never the key itself, so the event joins your account.

Opt inHow
Interactive setupAnswer y to the setup question (default No). The answer is saved.
Flaghermes tinyfish setup --share-usage
Configtinyfish.telemetry: true in Hermes config

Set tinyfish.telemetry: false to stop sending. TINYFISH_NO_TELEMETRY=1 (in your shell or ~/.hermes/.env) turns it off regardless of the other settings.

Development

python -m pip install -e . -r requirements-dev.txt  # dev deps are version-bounded in requirements-dev.txt
make lint
make test
scripts/e2e.sh  # real Hermes: validate, doctor, git install; live Search/Fetch with TINYFISH_API_KEY

License

MIT

README from the reviewed commit 2b29d5c; it updates when the author re-pins.

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section