Provider Routing
Provider Routing When using OpenRouter as your LLM provider, Hermes Agent supports provider routing — fine grained control over which underlying AI providers ha
- Section
- Core Features
- Source
- hermesbible.com/docs/user-guide/features/provider-routing
Provider Routing When using OpenRouter as your LLM provider, Hermes Agent supports provider routing — fine grained control over which underlying AI providers ha
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Configuration
- Options
- sort
- only
- ignore
- order
- require_parameters
- data_collection
- Practical Examples
- Optimize for Cost
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
Configuration
Maps configuration to the Core Features documentation path, with the source page reserved for exact commands and updates.
Options
Maps options to the Core Features documentation path, with the source page reserved for exact commands and updates.
sort
Maps sort to the Core Features documentation path, with the source page reserved for exact commands and updates.
only
Maps only to the Core Features documentation path, with the source page reserved for exact commands and updates.
ignore
Maps ignore to the Core Features documentation path, with the source page reserved for exact commands and updates.
order
Maps order to the Core Features documentation path, with the source page reserved for exact commands and updates.
require_parameters
Maps require_parameters to the Core Features documentation path, with the source page reserved for exact commands and updates.
data_collection
Maps data_collection 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: Configuration, Options, sort, only, ignore. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: provider, routing, openrouter, supports, grained. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for provider routing before applying exact upstream commands.
Open the source anchor for Configuration and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
- Start with the source section for Configuration; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Options if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Set provider, token, and retry limits before scaling the workflow beyond a single test run.
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