Repository navigation
feat(providers): add Astraflow (UCloud) OpenAI-compatible provider - #5964
Closed
diegosouzapw wants to merge 1 commit into
Closed
diegosouzapw wants to merge 1 commit into
diegosouzapw wants to merge 1 commit into
Conversation
Adds Astraflow (UCloud/UModelVerse) as an OpenAI-compatible, BYOK API-key provider pair: `astraflow` (global) and `astraflow-cn` (China). Both use passthrough model resolution (no fixed catalog), bearer API-key auth, and mirror the existing minimax/minimax-cn global+CN pair pattern. Base URLs point at the vendor's inference domains (behind UCloud's edge WAF), not the astraflow.ucloud-global.com / astraflow.ucloud.cn marketing sites: - global: https://api-us-ca.umodelverse.ai/v1/chat/completions - china: https://api.modelverse.cn/v1/chat/completions Co-authored-by: ucloudnb666 <k8sxtest@ucloud.cn> Inspired-by: decolua/9router#1127
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Owner
Author
|
Closing: Astraflow (astraflow/astraflow-cn) was previously added (PR #2486) and deliberately removed (PR #3054, 2026-06-02) as a dead/unreachable provider — its API endpoints returned 000/404/empty on HTTP probe. Re-verification during this port also got HTTP 404 on the inference paths. Re-adding a provider that was intentionally removed for being non-functional would be a regression. Reopen only with a live confirmation (working key hitting /v1/chat/completions) that the endpoints are back up. |
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.
Summary
astraflow(global) andastraflow-cn(China), following the existingminimax/minimax-cnglobal+CN pattern.passthroughModels: truewith an empty seed model list (no fixed catalog; matches the vendor's "OpenAI-compatible platform" positioning without hardcoding a specific model count).format: "openai",executor: "default".Base URL note
Base URLs are the vendor's inference domains (resolved behind UCloud's own edge WAF,
*.uewaf.com), not theastraflow.ucloud-global.com/astraflow.ucloud.cnmarketing sites:https://api-us-ca.umodelverse.ai/v1/chat/completionshttps://api.modelverse.cn/v1/chat/completionsBoth domains resolve via DNS to UCloud WAF infrastructure, which is a strong signal they are legitimate UCloud-operated endpoints. Direct HTTP validation could not be completed from this sandbox (no outbound network egress to arbitrary hosts). Best-effort — verify at first use.
Attribution
Thanks to @ucloudnb666
Changes
src/shared/constants/providers/apikey/gateways.ts—astraflow+astraflow-cngateway metadata (color#0052D9, websites).open-sse/config/providers/registry/astraflow/index.ts+open-sse/config/providers/registry/astraflow-cn/index.ts— registry entries.open-sse/config/providers/index.ts— wires both entries into the registry map.src/shared/constants/config.ts—PROVIDER_ENDPOINTSdisplay entries for both.CHANGELOG.md—[3.8.44]New Features entry.tests/unit/astraflow-provider.test.ts— new test file.Test plan
node --import tsx/esm scripts/check/check-provider-consistency.ts→ OK (173 REGISTRY entries, 245 canonical providers, 0 exceptions)node --import tsx/esm --test tests/unit/astraflow-provider.test.ts→ 5/5 passingnpm run typecheck:core→ cleannpm run check:cycles→ OK, no cycles