Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Model Provider Plugins

Building a Model Provider Plugin Model provider plugins declare an inference backend — an OpenAI compatible endpoint, an Anthropic Messages server, a Codex styl

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/model-provider-plugin

Building a Model Provider Plugin Model provider plugins declare an inference backend — an OpenAI compatible endpoint, an Anthropic Messages server, a Codex styl

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. How discovery works
  2. Directory structure
  3. Minimal example — a simple API-key provider
  4. ProviderProfile fields
  5. Overridable hooks
  6. Hook reference examples
  7. User overrides — replace a built-in without editing the repo
  8. api_mode selection
  9. Auth types
  10. Discovery timing
  11. Testing your plugin
  12. General PluginManager integration
  13. Distribute via pip
  14. Related pages

Section map

How discovery works

Maps how discovery works to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Directory structure

Maps directory structure to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Minimal example — a simple API-key provider

Maps minimal example — a simple api-key provider to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

ProviderProfile fields

Maps providerprofile fields to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Overridable hooks

Maps overridable hooks to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Hook reference examples

Maps hook reference examples to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

User overrides — replace a built-in without editing the repo

Maps user overrides — replace a built-in without editing the repo to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

api_mode selection

Maps api_mode selection 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: How discovery works, Directory structure, Minimal example — a simple API-key provider, ProviderProfile fields, Overridable hooks. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: model, provider, plugins, building, plugin. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

Use when you need orientation for model provider plugins before applying exact upstream commands.

Verify firstHow discovery works

Open the source anchor for How discovery works 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 Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for How discovery works; 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 Directory structure 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

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.

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