Skip to content

docs: document explicit api_mode for custom endpoints#7176

Open
believeyounger wants to merge 1 commit into
NousResearch:mainfrom
believeyounger:docs/custom-api-mode
Open

docs: document explicit api_mode for custom endpoints#7176
believeyounger wants to merge 1 commit into
NousResearch:mainfrom
believeyounger:docs/custom-api-mode

Conversation

@believeyounger

Copy link
Copy Markdown

Summary

  • document model.api_mode for custom endpoints in the providers guide
  • show an explicit codex_responses config example for OpenAI Responses-backed relays
  • clarify that explicit api_mode wins when set, while existing auto-detection remains the fallback

Why

Hermes already supports explicit model.api_mode for custom endpoints, but the custom endpoint docs only showed provider, base_url, and api_key. That makes Responses-backed relays easy to misconfigure and encourages brittle URL heuristics.

This PR makes the preferred path explicit in the docs without changing runtime behavior.

Test plan

  • documentation-only change
  • manually verified the new example matches Hermes' supported api_mode values (chat_completions, codex_responses, anthropic_messages)

@alt-glitch alt-glitch added type/docs Documentation improvements P3 Low — cosmetic, nice to have area/config Config system, migrations, profiles labels Apr 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config Config system, migrations, profiles P3 Low — cosmetic, nice to have type/docs Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants