iiRecord
Agentic AI Atlas · Hermes Provider Runtime
agent-runtime-impl:hermes.provider-runtimea5c.ai
II.
AgentRuntimeImpl JSON

agent-runtime-impl:hermes.provider-runtime

Structured · live

Hermes Provider Runtime json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · agent-stack/hermes/hermes-provider-runtime.yamlCluster · agent-stack
Record JSON
{
  "id": "agent-runtime-impl:hermes.provider-runtime",
  "_kind": "AgentRuntimeImpl",
  "_file": "agent-stack/hermes/hermes-provider-runtime.yaml",
  "_cluster": "agent-stack",
  "attributes": {
    "displayName": "Hermes Provider Runtime",
    "agentVersionId": "agentVersion:hermes:ge-0-0-0",
    "description": "Plugin-based provider runtime resolver shared across CLI, gateway,\ncron jobs, ACP, and auxiliary model calls. Providers declared in\nplugins/model-providers/<name>/ and registered via register_provider().\n30+ provider integrations with OAuth, alias resolution, fallback chains,\nand auxiliary model routing for side tasks.\n",
    "keyFiles": [
      "hermes_cli/runtime_provider.py",
      "hermes_cli/auth.py",
      "hermes_cli/model_switch.py",
      "plugins/model-providers/"
    ],
    "resolutionPrecedence": [
      "Explicit CLI/runtime request",
      "config.yaml model/provider",
      "Environment variables",
      "Provider-specific defaults or auto-resolution"
    ],
    "providerFamilies": [
      "OpenRouter, Nous Portal, OpenAI Codex",
      "Anthropic (native), Google Gemini, DeepSeek",
      "AWS Bedrock, Azure Foundry, NVIDIA NIM",
      "Ollama Cloud, LM Studio",
      "Custom OpenAI-compatible endpoints"
    ],
    "fallbackBehavior": "Ordered list of (provider, model) pairs tried sequentially on errors.\nActivation triggers: invalid API responses after max retries, non-retryable\nclient errors (401/403/404), transient errors (429/500/502/503) after\nretry exhaustion. Subagents inherit parent settings but not fallback config.\n",
    "auxiliaryRouting": "Tasks like vision, summarization, and memory operations route to\nindependent providers using the same runtime resolution path.\n",
    "ourEquivalent": "packages/adapters/proxy/ handles cross-harness provider routing.\nIndividual harnesses own their own provider resolution. Our adapters\nproxy provides a multi-harness layer that Hermes lacks -- Hermes\nprovider resolution is internal to a single agent instance.\n"
  },
  "outgoingEdges": [
    {
      "from": "agent-runtime-impl:hermes.provider-runtime",
      "to": "layer:5-agent-runtime",
      "kind": "realizes",
      "attributes": {}
    },
    {
      "from": "agent-runtime-impl:hermes.provider-runtime",
      "to": "agent:hermes",
      "kind": "part_of",
      "attributes": {}
    }
  ],
  "incomingEdges": []
}