Provider Runtime Resolution
Hermes has a shared provider runtime resolver used across: CLI gateway cron jobs ACP auxiliary model calls Primary implementation: — credential resolution, — pr
- Section
- Developer Guide
- Source
- hermesbible.com/docs/developer-guide/provider-runtime
Hermes has a shared provider runtime resolver used across: CLI gateway cron jobs ACP auxiliary model calls Primary implementation: — credential resolution, — pr
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Resolution precedence
- Providers
- Output of runtime resolution
- Why this matters
- OpenRouter and custom OpenAI-compatible base URLs
- Native Anthropic path
- OpenAI Codex path
- Auxiliary model routing
- Fallback models
- How it works internally
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
Resolution precedence
Maps resolution precedence to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Providers
Maps providers to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Output of runtime resolution
Maps output of runtime resolution to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Why this matters
Maps why this matters to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
OpenRouter and custom OpenAI-compatible base URLs
Maps openrouter and custom openai-compatible base urls to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Native Anthropic path
Maps native anthropic path to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
OpenAI Codex path
Maps openai codex path to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Auxiliary model routing
Maps auxiliary model routing to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Developer Guide 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: Resolution precedence, Providers, Output of runtime resolution, Why this matters, OpenRouter and custom OpenAI-compatible base URLs. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: provider, runtime, resolution, resolver, across. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for provider runtime resolution before applying exact upstream commands.
Open the source anchor for Resolution precedence 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 Developer Guide, then open the linked source page for exact current syntax.
- Start with the source section for Resolution precedence; 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 Providers 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
Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
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