Models & Providers guides

A practical guide to choose a model provider in a verified Hermes/Rocky workflow.

A practical guide to openrouter provider setup in a verified Hermes/Rocky workflow.

A practical guide to anthropic provider setup in a verified Hermes/Rocky workflow.

A practical guide to openai codex provider setup in a verified Hermes/Rocky workflow.

A practical guide to gemini provider setup in a verified Hermes/Rocky workflow.

A practical guide to local model provider setup in a verified Hermes/Rocky workflow.

A practical guide to credential pools in a verified Hermes/Rocky workflow.

How to think about provider authentication, credential pools, quota exhaustion, and fallback models in Hermes without exposing secrets.

A practical model-selection guide for Rocky workflows: coding, web research, writing, vision, media, automation, and low-cost summaries.

A practical guide to choosing primary and fallback model providers without hard-coding secrets or building workflows around one fragile endpoint.

A practical guide to choosing model providers, fallback paths, and cost tiers for Rocky without making unsupported claims.

Choose model tiers, route premium work intentionally, and handle provider failures without unsupported promises.

Prevent surprise cost and authentication failures by treating scheduled-job model selection, credentials, workdirs, and prompts as release-time configuration.

Understand how Hermes resolves provider, model, API mode, base URL, credential source, auxiliary routes, and fallback without leaking keys across endpoints.

Choose a custom, plugin, or native path and verify auth, model discovery, runtime resolution, auxiliary routing, protocol adapters, tests, and docs.

Use one OAuth-backed Nous Portal setup for model access and managed web, image, speech, browser, and optional sandbox tools.

Connect Hermes to llama.cpp or an MLX server on Apple Silicon with realistic memory, context, networking, and verification gates.

Configure Hermes for Amazon Bedrock’s native Converse API with IAM credentials, regional model discovery, inference profiles, and a verified first request.

Connect Hermes to Microsoft Foundry or Azure OpenAI with API-key or Microsoft Entra ID authentication and the correct endpoint transport.

Route Hermes to Gemini on Vertex AI with service-account or Application Default Credentials and automatically refreshed OAuth tokens.

Use Hermes’ xAI device-code OAuth path for an eligible SuperGrok or X Premium+ account, with explicit entitlement and API-key fallback checks.

Choose, configure, and verify Hermes’ opt-in Codex app-server runtime while preserving clear tool, sandbox, plugin, and rollback boundaries.

Connect Hermes to Ollama’s local OpenAI-compatible endpoint with realistic hardware, context-window, tool-calling, privacy, and fallback checks.

Connect the global MiniMax provider through Hermes’ browser or headless OAuth flow and verify token refresh, region, and model selection.

Build a named Mixture of Agents preset with advisory reference models, one acting aggregator, and explicit cost, cadence, and privacy controls.

Use priority processing only when faster model responses justify provider-specific cost and availability tradeoffs, then verify the active mode before important work.

Control aggregator sub-provider selection by price, latency, throughput, capability support, and data-collection policy.

Set provider-wide and model-specific timeouts without confusing total request limits, stale-call detection, stream gaps, or local-model prefill.

Design a cross-provider failover chain that preserves sessions, controls auxiliary routing, and avoids costly fallback surprises.

Use Hermes model-catalog manifests, caching, and bundled snapshots to balance fresh curation with reliable offline selection.