feat(providers): Support DeepInfra as an LLM provider

[ats3v]

What does this PR do?

Adds DeepInfra as a first-class LLM provider, giving users access to 100+ top open source and frontier models (GLM-5, DeepSeek-V3+, Qwen3+, Kimi-K2+, Nemotron, etc.) via a single API key.

DeepInfra is one of the largest open-model inference platforms and a top provider on OpenRouter. This integration lets users connect directly — lower latency, simpler billing, no middleman.

The implementation follows the exact same pattern as HuggingFace, KiloCode, and other API-key providers. Purely additive — no changes to existing provider behavior.

Related Issue

N/A — new provider integration.

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 — Register deepinfra in PROVIDER_REGISTRY (api_key auth, https://api.deepinfra.com/v1/openai) + deep-infra alias
• hermes_cli/config.py — Add DEEPINFRA_API_KEY and DEEPINFRA_BASE_URL to OPTIONAL_ENV_VARS
• hermes_cli/models.py — Add 19 curated models, provider label, alias, and display ordering
• hermes_cli/main.py — Add to provider selection menu, --provider CLI choices, and _model_flow_api_key_provider dispatch
• agent/auxiliary_client.py — Register mistralai/Mistral-Nemo-Instruct-2407 as default auxiliary model (fast, cheap, reliable for summarization)
• agent/model_metadata.py — Add deepinfra/deep-infra to provider prefixes and api.deepinfra.com to URL-to-provider mapping
• .env.example / cli-config.yaml.example — Document the new env var and provider option
• tests/test_api_key_providers.py — 7 new tests: registration, env vars, base URL, alias resolution, auto-detection, model list consistency

How to Test

1. Setup:

   # Get a key at https://deepinfra.com/dash/api_keys
   echo "DEEPINFRA_API_KEY=<your-key>" >> ~/.hermes/.env
   

2. Provider selection:

hermes model # Select "DeepInfra" from the menu

3. Direct chat:

hermes chat --provider deepinfra -m "deepseek-ai/DeepSeek-V3-0324" -q "Hello"

4. Tool calling (agent loop):

hermes chat --provider deepinfra -m "deepseek-ai/DeepSeek-V3-0324" -t terminal -q "List files in the current directory"

5. Auto-detection:

With only DEEPINFRA_API_KEY set (no other provider keys), hermes chat auto-selects DeepInfra.

6. Unit tests:

pytest tests/test_api_key_providers.py -k deepinfra -v

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: Ubuntu 24.04 on WSL2.0

Documentation & Housekeeping

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

Screenshots / Logs

[ats3v]

@alt-glitch PR up to date and passing all tests. Would really appreciate a review. Thank you!