Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Subscription Proxy

The subscription proxy is a local HTTP server that lets external apps — OpenViking, Karakeep, Open WebUI, anything that speaks OpenAI compatible chat completion

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/subscription-proxy

The subscription proxy is a local HTTP server that lets external apps — OpenViking, Karakeep, Open WebUI, anything that speaks OpenAI compatible chat completion

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. Log into your provider (one-time)
  3. 2. Start the proxy
  4. 3. Point your app at it
  5. Available providers
  6. Check status
  7. Allowed paths
  8. Configuring OpenViking to use Portal
  9. Configuring Karakeep (or any bookmark/summarizer app)
  10. Exposing on LAN
  11. Rate limits
  12. Architecture
  13. Future: more OAuth providers

Section map

Quick Start

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

1. Log into your provider (one-time)

Maps 1. log into your provider (one-time) to the Core Features documentation path, with the source page reserved for exact commands and updates.

2. Start the proxy

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

3. Point your app at it

Maps 3. point your app at it to the Core Features documentation path, with the source page reserved for exact commands and updates.

Available providers

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

Check status

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

Allowed paths

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

Configuring OpenViking to use Portal

Maps configuring openviking to use portal 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. Log into your provider (one-time), 2. Start the proxy, 3. Point your app at it, Available providers. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: subscription, proxy, local, server, external. 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 subscription proxy 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. Log into your provider (one-time) 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

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

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