Skip to content

feat(provider): add DaoXE multi-model gateway#6854

Open
seven7763 wants to merge 1 commit into
ChatGPTNextWeb:mainfrom
seven7763:feat/add-daoxe-provider
Open

feat(provider): add DaoXE multi-model gateway#6854
seven7763 wants to merge 1 commit into
ChatGPTNextWeb:mainfrom
seven7763:feat/add-daoxe-provider

Conversation

@seven7763

Copy link
Copy Markdown

Summary

Add DaoXE as a built-in OpenAI-compatible provider for NextChat, following the SiliconFlow / 302.AI pattern.

  • Base: https://daoxe.com (Chat Completions at /v1/chat/completions)
  • Settings: DaoXE endpoint + API key
  • Runtime model list via GET /v1/models (account-scoped; no static public price list)
  • Multi-model multi-protocol gateway; this integration uses Chat Completions only
  • Not available in mainland China

Files

  • app/client/platforms/daoxe.ts, app/api/daoxe.ts
  • wiring in constant.ts, access.ts, client/api.ts, auth.ts, server.ts, settings.tsx, locales, .env.template

I maintain DaoXE. Examples: https://github.com/seven7763/DaoXE-AI

Why

NextChat is widely used among price-sensitive builders in Vietnam and CIS Russian-speaking communities. A named provider is clearer than manual OpenAI custom base URL.

Test plan

  • Settings → select DaoXE → set API key from https://daoxe.com/dashboard
  • Models refresh from GET /v1/models
  • Send a short chat (stream on/off)
  • Optional: DAOXE_API_KEY server env for reverse proxy path

Add DaoXE as a built-in OpenAI-compatible provider (Chat Completions at
https://daoxe.com/v1). Model IDs come from account GET /v1/models;
no static public price list. Not available in mainland China.

Signed-off-by: seven7763 <seven7763@users.noreply.github.com>
@RheagalFire RheagalFire mentioned this pull request Jul 16, 2026
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant