Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Nous Tool Gateway

One subscription. Every tool built in. The Tool Gateway is included with every paid Nous Portal subscription. It routes Hermes' tool calls — web search, image g

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/tool-gateway

One subscription. Every tool built in. The Tool Gateway is included with every paid Nous Portal subscription. It routes Hermes' tool calls — web search, image g

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. What's included
  2. Why it's here
  3. Get started
  4. Eligibility
  5. Mix and match
  6. Using individual image models
  7. Configuration reference
  8. Per-tool use_gateway flag
  9. Disabling the gateway
  10. Self-hosted gateway (advanced)
  11. FAQ
  12. Does it work with Telegram / Discord / the other messaging gateways?
  13. What happens if my subscription expires?
  14. Can I see usage or costs per tool?

Section map

What's included

Maps what's included to the Core Features documentation path, with the source page reserved for exact commands and updates.

Why it's here

Maps why it's here to the Core Features documentation path, with the source page reserved for exact commands and updates.

Get started

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

Eligibility

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

Mix and match

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

Using individual image models

Maps using individual image models to the Core Features documentation path, with the source page reserved for exact commands and updates.

Configuration reference

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

Per-tool use_gateway flag

Maps per-tool use_gateway flag 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: What's included, Why it's here, Get started, Eligibility, Mix and match. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: gateway, subscription., every, included, portal. 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 nous tool gateway before applying exact upstream commands.

Verify firstWhat's included

Open the source anchor for What's included 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 What's included; 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 Why it's here 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

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

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

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