feat: add DaoXE as an OpenAI-compatible provider alias - #4246
Conversation
Mirrors the OVHcloud alias-provider pattern: alias entry with DAOXE_API_KEY, auto-config support, system-message merge behavior shared with the other OpenAI-compatible gateway aliases, provider docs page, example recipe, and test coverage across the touched packages. The models.dev catalog already carries the daoxe entry, so the default model resolves through it. Signed-off-by: seven7763 <seven7763@users.noreply.github.com>
aheritier
added
area/config
|
👋 Some commits in this PR are not signed and verified by GitHub. Please sign your commits with a GPG or SSH key registered in your GitHub account, then force-push. |
|
Commits that are not verified: |
|
See GitHub's guide on signing commits for setup instructions. I've added |
|
👋 Some commits in this PR are not signed and verified by GitHub. Please sign your commits with a GPG or SSH key registered in your GitHub account, then force-push. Commits that are not verified: See GitHub's guide on signing commits for setup instructions. I've added |
2 participants
Adds DaoXE (https://daoxe.com) as a built-in OpenAI-compatible alias provider, following the OVHcloud alias-provider pattern (#3343):
DAOXE_API_KEYenv-var auth and theapi.daoxe.com/v1base URLdaoxeentrypkg/model/provider,pkg/config, and the OpenAI clientDisclosure: I'm affiliated with DaoXE; this contribution only adds standard OpenAI-compatible client wiring, no bundled keys or credentials.