Image Generation Provider Plugins
Building an Image Generation Provider Plugin Image gen provider plugins register a backend that services every tool call — DALL·E, gpt image, Grok, Flux, Imagen
- Section
- Developer Guide
- Source
- hermesbible.com/docs/developer-guide/image-gen-provider-plugin
Building an Image Generation Provider Plugin Image gen provider plugins register a backend that services every tool call — DALL·E, gpt image, Grok, Flux, Imagen
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- How discovery works
- Directory structure
- The ImageGenProvider ABC
- plugin.yaml
- ABC reference
- Response format
- Handling base64 vs URL output
- User overrides
- Testing
- Reference implementations
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
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.
The ImageGenProvider ABC
Maps the imagegenprovider abc to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
plugin.yaml
Maps plugin.yaml to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
ABC reference
Maps abc reference to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Response format
Maps response format to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
Handling base64 vs URL output
Maps handling base64 vs url output to the Developer Guide documentation path, with the source page reserved for exact commands and updates.
User overrides
Maps user overrides 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, The ImageGenProvider ABC, plugin.yaml, ABC reference. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: image, generation, provider, plugins, building. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for image generation provider plugins before applying exact upstream commands.
Open the source anchor for How discovery works 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 How discovery works; 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 Directory structure 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