Nous Portal
Nous Portal is Nous Research's unified subscription gateway and the recommended way to run Hermes Agent . One OAuth login replaces the juggling act of separate
- Section
- Integrations
- Source
- hermesbible.com/docs/integrations/nous-portal
Nous Portal is Nous Research's unified subscription gateway and the recommended way to run Hermes Agent . One OAuth login replaces the juggling act of separate
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- What's in the subscription
- 300+ frontier models, one bill
- The Nous Tool Gateway
- Nous Chat
- No credentials in your dotfiles
- Cross-platform parity
- A note on Hermes 4
- Setup
- Fresh install — one command
- Existing install — add Portal alongside other providers
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
- What's in the subscription
- 300+ frontier models, one bill
- The Nous Tool Gateway
- Nous Chat
- No credentials in your dotfiles
- Cross-platform parity
- A note on Hermes 4
- Setup
- Fresh install — one command
- Existing install — add Portal alongside other providers
- Headless / SSH / remote setup
- Profile setup
- Using the Portal day-to-day
- Inspecting what's wired up
Section map
What's in the subscription
Maps what's in the subscription to the Integrations documentation path, with the source page reserved for exact commands and updates.
300+ frontier models, one bill
Maps 300+ frontier models, one bill to the Integrations documentation path, with the source page reserved for exact commands and updates.
The Nous Tool Gateway
Maps the nous tool gateway to the Integrations documentation path, with the source page reserved for exact commands and updates.
Nous Chat
Maps nous chat to the Integrations documentation path, with the source page reserved for exact commands and updates.
No credentials in your dotfiles
Maps no credentials in your dotfiles to the Integrations documentation path, with the source page reserved for exact commands and updates.
Cross-platform parity
Maps cross-platform parity to the Integrations documentation path, with the source page reserved for exact commands and updates.
A note on Hermes 4
Maps a note on hermes 4 to the Integrations documentation path, with the source page reserved for exact commands and updates.
Setup
Maps setup to the Integrations documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Integrations 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: What's in the subscription, 300+ frontier models, one bill, The Nous Tool Gateway, Nous Chat, No credentials in your dotfiles. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: portal, research, unified, subscription, gateway. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for nous portal before applying exact upstream commands.
Open the source anchor for What's in the subscription 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 Integrations, then open the linked source page for exact current syntax.
- Start with the source section for What's in the subscription; 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 300+ frontier models, one bill 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
Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.
Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.
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