Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Web Search & Extract

Web Search & Extract Hermes Agent includes two model callable web tools backed by multiple providers: — search the web and return ranked results — fetch and ext

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/web-search

Web Search & Extract Hermes Agent includes two model callable web tools backed by multiple providers: — search the web and return ranked results — fetch and ext

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Backends
  2. How web_extract handles long pages
  3. Which model does the summarizing?
  4. When summarization gets in the way
  5. Setup
  6. Quick setup via hermes tools
  7. Firecrawl (default)
  8. SearXNG (free, self-hosted)
  9. Option A — Self-host with Docker (recommended)
  10. Option B — Use a public instance
  11. Pair SearXNG with an extract provider
  12. Tavily
  13. Exa
  14. Parallel

Section map

Backends

Maps backends to the Core Features documentation path, with the source page reserved for exact commands and updates.

How web_extract handles long pages

Maps how web_extract handles long pages to the Core Features documentation path, with the source page reserved for exact commands and updates.

Which model does the summarizing?

Maps which model does the summarizing? to the Core Features documentation path, with the source page reserved for exact commands and updates.

When summarization gets in the way

Maps when summarization gets in the way to the Core Features documentation path, with the source page reserved for exact commands and updates.

Setup

Maps setup to the Core Features documentation path, with the source page reserved for exact commands and updates.

Quick setup via hermes tools

Maps quick setup via hermes tools to the Core Features documentation path, with the source page reserved for exact commands and updates.

Firecrawl (default)

Maps firecrawl (default) to the Core Features documentation path, with the source page reserved for exact commands and updates.

SearXNG (free, self-hosted)

Maps searxng (free, self-hosted) to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Backends, How web_extract handles long pages, Which model does the summarizing?, When summarization gets in the way, Setup. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: search, extract, includes, model, callable. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for web search & extract before applying exact upstream commands.

Verify firstBackends

Open the source anchor for Backends and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Backends; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for How web_extract handles long pages if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page