What does this PR do?

Adds NVIDIA NIM as a first-class provider: ProviderConfig in auth.py, HermesOverlay in providers.py, curated models (Nemotron plus other open source models hosted on build.nvidia.com), URL mapping in model_metadata.py, aliases (nim, nvidia-nim, build-nvidia, nemotron), and env var tests.

Docs updated: providers page, quickstart table, fallback providers table, and README provider list.

Related Issue

#9106

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• hermes_cli/auth.py — add PROVIDER_REGISTRY["nvidia"] entry (base URL https://integrate.api.nvidia.com/v1, env vars NVIDIA_API_KEY / NVIDIA_BASE_URL)
• hermes_cli/providers.py — add HERMES_OVERLAYS["nvidia"] (openai_chat transport) and aliases nim, nvidia-nim, build-nvidia, nemotron
• hermes_cli/models.py — add NVIDIA to CANONICAL_PROVIDERS (so it appears in hermes model / hermes setup), add _PROVIDER_MODELS["nvidia"] with 5 curated models (Nemotron 3 Super, Nemotron 3 Nano, GLM 5, Kimi K2.5, MiniMax M2.5), extend _PROVIDER_ALIASES
• agent/model_metadata.py — add provider prefixes and integrate.api.nvidia.com → nvidia URL mapping
• tests/hermes_cli/test_api_key_providers.py — parametrized registry test + test_nvidia_env_vars
• website/docs/integrations/providers.md — new "NVIDIA NIM" section with cloud + local NIM usage and curated model table
• website/docs/getting-started/quickstart.md — add NVIDIA NIM row to provider table
• website/docs/user-guide/features/fallback-providers.md — add NVIDIA NIM row
• README.md — add NVIDIA NIM link to supported providers list

How to Test

1. pytest tests/hermes_cli/test_api_key_providers.py -q — 129 tests pass, including new test_nvidia_env_vars
2. hermes model — NVIDIA NIM appears in the provider list; select it, pick nvidia/nemotron-3-super-120b-a12b
3. Export NVIDIA_API_KEY=<your-build.nvidia.com-key> (free at https://build.nvidia.com), then hermes chat --provider nvidia --model nvidia/nemotron-3-super-120b-a12b -q "hello" — routes to integrate.api.nvidia.com/v1
4. For local NIM: NVIDIA_BASE_URL=http://localhost:8000/v1 hermes chat --provider nvidia --model nvidia/nemotron-3-super-120b-a12b
5. Aliases: --provider nim / --provider nvidia-nim / --provider build-nvidia / --provider nemotron all resolve to nvidia

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS 15.x

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• [N/A] I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• [N/A] I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• [N/A] I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• [N/A] I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs