Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Plugin LLM Access

is the supported way for a plugin to make an LLM call. Chat completion, structured extraction, sync, async, with or without images — same surface, same trust ga

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/plugin-llm-access

is the supported way for a plugin to make an LLM call. Chat completion, structured extraction, sync, async, with or without images — same surface, same trust ga

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. The smallest possible call
  2. A more complete chat example
  3. Structured output
  4. What this lane gives you
  5. Quick start
  6. Chat completion — /tldr
  7. Structured extraction — /paste-to-tasks
  8. When to use which
  9. API surface
  10. complete()
  11. complete_structured()
  12. Async
  13. Result attributes
  14. Trust gate

Section map

The smallest possible call

Maps the smallest possible call to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

A more complete chat example

Maps a more complete chat example to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Structured output

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

What this lane gives you

Maps what this lane gives you to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Quick start

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

Chat completion — /tldr

Maps chat completion — /tldr to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Structured extraction — /paste-to-tasks

Maps structured extraction — /paste-to-tasks to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

When to use which

Maps when to use which 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: The smallest possible call, A more complete chat example, Structured output, What this lane gives you, Quick start. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: plugin, access, supported, call., completion. 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 plugin llm access before applying exact upstream commands.

Verify firstThe smallest possible call

Open the source anchor for The smallest possible call 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 The smallest possible call; 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 A more complete chat example 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

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