Hermes BibleUnofficial Docs
← All docs Docs / Core Features

API Server

The API server exposes hermes agent as an OpenAI compatible HTTP endpoint. Any frontend that speaks the OpenAI format — Open WebUI, LobeChat, LibreChat, NextCha

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/api-server

The API server exposes hermes agent as an OpenAI compatible HTTP endpoint. Any frontend that speaks the OpenAI format — Open WebUI, LobeChat, LibreChat, NextCha

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. Quick Start
  2. 1. Enable the API server
  3. 2. Start the gateway
  4. 3. Connect a frontend
  5. Endpoints
  6. POST /v1/chat/completions
  7. POST /v1/responses
  8. Multi-turn with previous_response_id
  9. Named conversations
  10. GET /v1/responses/\{id\}
  11. DELETE /v1/responses/\{id\}
  12. GET /v1/models
  13. GET /v1/capabilities
  14. GET /health

Section map

Quick Start

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

1. Enable the API server

Maps 1. enable the api server to the Core Features documentation path, with the source page reserved for exact commands and updates.

2. Start the gateway

Maps 2. start the gateway to the Core Features documentation path, with the source page reserved for exact commands and updates.

3. Connect a frontend

Maps 3. connect a frontend to the Core Features documentation path, with the source page reserved for exact commands and updates.

Endpoints

Maps endpoints to the Core Features documentation path, with the source page reserved for exact commands and updates.

POST /v1/chat/completions

Maps post /v1/chat/completions to the Core Features documentation path, with the source page reserved for exact commands and updates.

POST /v1/responses

Maps post /v1/responses to the Core Features documentation path, with the source page reserved for exact commands and updates.

GET /v1/responses/\{id\}

Maps get /v1/responses/\{id\} 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: Quick Start, 1. Enable the API server, 2. Start the gateway, 3. Connect a frontend, Endpoints. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: server, exposes, openai, compatible, endpoint.. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for api server before applying exact upstream commands.

Verify firstQuick Start

Open the source anchor for Quick Start 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 Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Quick Start; 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 1. Enable the API server 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

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

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