Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix Add DeepInfra as an official LLM provider [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#15709•Fetched 2026-04-26 05:25:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ZinkDifferentZinkDifferent
Participants
alt-glitchalt-glitchZinkDifferentZinkDifferent
Timeline (top)
labeled ×3commented ×1
RAW_BUFFERClick to expand / collapse

Feature Description

Add DeepInfra as a first-class supported provider in Hermes Agent, alongside Ollama, OpenRouter, and Google.

Motivation

DeepInfra offers highly competitive pricing and low-latency access to a wide range of open-weight models (Llama 3, Qwen, Mistral, etc.) using a stable OpenAI-compatible API. While it can currently be used via the custom_providers configuration, having it as a native provider would simplify setup (especially for new users) and allow for better integration with the credential pool and model discovery.

Proposed Solution

  • Add deepinfra to the PROVIDER_REGISTRY in hermes_cli/auth.py.
  • Define the default base_url as https://api.deepinfra.com/v1/openai.
  • Ensure DEEPINFRA_API_KEY is recognized as the standard environment variable.
  • (Optional) Add a dedicated setup flow in hermes setup provider.

Alternatives Considered

Continuing to use custom_providers, which requires manual JSON configuration in config.yaml and doesn't provide the same "out of the box" experience as supported providers.

extent analysis

TL;DR

Add DeepInfra as a native provider in Hermes Agent by updating the PROVIDER_REGISTRY and recognizing the DEEPINFRA_API_KEY environment variable.

Guidance

  • Update hermes_cli/auth.py to include deepinfra in the PROVIDER_REGISTRY.
  • Define the default base_url for DeepInfra as https://api.deepinfra.com/v1/openai.
  • Ensure the code recognizes DEEPINFRA_API_KEY as the standard environment variable for authentication.
  • Consider adding a dedicated setup flow in hermes setup provider for a smoother user experience.

Example

# hermes_cli/auth.py
PROVIDER_REGISTRY = {
    # ... existing providers ...
    'deepinfra': {
        'base_url': 'https://api.deepinfra.com/v1/openai',
        'api_key_env_var': 'DEEPINFRA_API_KEY'
    }
}

Notes

This solution assumes that the DeepInfra API is compatible with the existing provider interface in Hermes Agent. Additional testing and validation may be necessary to ensure seamless integration.

Recommendation

Apply the proposed solution to add DeepInfra as a native provider, as it simplifies setup and improves integration with the credential pool and model discovery.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#memory optimization#batch processing#GPU compatibility#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Add DeepInfra as an official LLM provider [1 comments, 2 participants]