hermes-models

Topics in the source

• Hermes Models & Providers
• When to Use
• Rules
• Proof
• References

Routing is configuration plus proof. config get proves neither the route nor the metadata. | You hear / see | Load | |---|---| | change the default model / add a provider / change an endpoint | rules below + references/model-switching.md | | a model 404s, does not support the responses endpoint | references/custom-providers.md | | "run the subagent on a cheaper model" | references/delegation-routing.md | | profile models/keys do not apply, only root works | references/delegation-routing.md → per-profile provider | | config drifts between root and profiles | references/config-drift.md | | vision / imagegen errors, auto routing | references/config-drift.md | | declare contextlength / metadata for a model | references/provider-metadata-audit.md | | a relay's effort/cost/streaming behavior looks wrong | references/model-endpoint-matrix.md | Not for: another agent harness's endpoints (pi/omp/opencode/dsh); those follow that harness's own model configuration. 1. Transport is per model, not per endpoint. One proxy serves /v1/responses for some ids and /v1/chat/completions for others; probe both before concluding a capability is missing. 2. Provider entries live under top-level providers:;

This is an excerpt. Refer to the complete source and its current requirements.