feat(ai): add DaoXE as a model provider - #13783
Open
seven7763 wants to merge 1 commit into
Open
Conversation
DaoXE (https://daoxe.com) is an OpenAI-compatible multi-model LLM gateway that also serves Anthropic Messages. Register it in the agent provider catalog next to OpenRouter with model discovery on the OpenAI-compatible routes, and add its provider logo using an inline SVG data URI so no binary asset is added to the repository.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it?
Adds DaoXE as a selectable AI agent model provider. DaoXE is an
OpenAI-compatible multi-model LLM gateway (hundreds of models behind one API key) that
also serves Anthropic Messages on the same account, so it can back both OpenAI-type and
Claude-type agent flows in 1Panel.
Affiliation disclosure for transparency: I maintain this gateway, and this PR registers
it in the provider catalog the same way existing gateways (OpenRouter, DeepSeek, ...)
are registered.
Summary of your change
agent/app/provider/catalog.go: newdaoxeentry (Sort 57, next to OpenRouter) withopenai-completions/openai-responses/openai-embeddingsonhttps://api.daoxe.com/v1(model discovery enabled — standardGET /v1/models) and ananthropic-messagesconfig onhttps://api.daoxe.com(x-api-key default, beareroptional). Added to
legacyModelPrefixes. No hardcoded model list: models arediscovered at runtime, so the entry stays correct as the catalog behind it changes.
frontend/src/utils/agent-provider-logo.ts: provider logo, inlined as an SVG data URIso no binary asset is added to the repo (happy to switch to a committed
ai-providers/daoxe.svgif maintainers prefer the file convention).verify.go/openclaw.go/ agents special-cases needed: DaoXE is a keyed providerusing the standard bearer-verification path (unlike ollama/llmman local runners).
Testing:
go build/go vet/gofmt -lonagent/app/provider,agent/app/service,agent/utils/terminal/aipass;prettier --checkandeslintpasson the touched frontend file; live
GET /v1/modelson the gateway verified to return thestandard
{"data": [...]}shape used byDiscoverModels. Not yet run against a live1Panel/OpenClaw deployment.
Please indicate you've done the following: