fix: 媒体技能改用动态 provider 发现,移除硬编码 providerId

minimax-music-gen (1.1.2 → 1.1.3):
- providerId: "provider-minimax-media-001" → provider: "minimax" + serviceType: "music_gen"

minimax-video-gen (1.2.1 → 1.2.2):
- providerId: "provider-minimax-media-001" → provider: "minimax" + serviceType: "video_gen"

此前硬编码的 provider-minimax-media-001 在系统中不存在,导致使用
MiniMax Token Plan 或 Coding Plan 时文生音乐/文生视频功能无法路由。
改为 slug + serviceType 动态发现后,无论用户启用按量 API 还是
Token/Coding Plan,findProvider() 都能正确匹配。
This commit is contained in:
2026-05-09 23:25:38 +08:00
parent e346cd0123
commit 038f3542bd
4 changed files with 36 additions and 22 deletions

View File

@@ -7,7 +7,7 @@ description: >-
Use when 用户提到 生成视频、文生视频、AI 视频、创建视频、视频生成、
动画生成、MiniMax 视频、海螺、Hailuo、图片变视频、图生视频。
license: Complete terms in LICENSE.txt
version: 1.2.1
version: 1.2.2
type: procedural
risk_level: low
status: enabled
@@ -76,7 +76,7 @@ market:
### Prerequisites
- The user has already configured the MiniMax Media Provider in Resource Manager → Compute and entered the API Key
- The user has already configured and enabled a MiniMax Provider (regular API or Token Plan) in Resource Manager → Compute and entered the API Key
- agent-service is running
### Core Concept: Three-Step Asynchronous Flow
@@ -107,7 +107,8 @@ PORT=$(cat ~/.desirecore/agent-service.port)
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
-H "Content-Type: application/json" \
-d '{
"providerId": "provider-minimax-media-001",
"provider": "minimax",
"serviceType": "video_gen",
"endpoint": "/video_generation",
"body": {
"model": "MiniMax-Hailuo-2.3",
@@ -130,7 +131,8 @@ PORT=$(cat ~/.desirecore/agent-service.port)
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
-H "Content-Type: application/json" \
-d '{
"providerId": "provider-minimax-media-001",
"provider": "minimax",
"serviceType": "video_gen",
"endpoint": "/video_generation",
"body": {
"model": "MiniMax-Hailuo-2.3",
@@ -151,7 +153,8 @@ TASK_ID="task_id returned from step 1"
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
-H "Content-Type: application/json" \
-d "{
\"providerId\": \"provider-minimax-media-001\",
\"provider\": \"minimax\",
\"serviceType\": \"video_gen\",
\"endpoint\": \"/query/video_generation?task_id=${TASK_ID}\",
\"method\": \"GET\",
\"responseType\": \"json\"
@@ -192,7 +195,8 @@ FILE_ID="file_id returned from step 2"
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
-H "Content-Type: application/json" \
-d "{
\"providerId\": \"provider-minimax-media-001\",
\"provider\": \"minimax\",
\"serviceType\": \"video_gen\",
\"endpoint\": \"/files/retrieve?file_id=${FILE_ID}\",
\"method\": \"GET\",
\"responseType\": \"json\"
@@ -226,7 +230,7 @@ Write Markdown image syntax directly in your reply (the frontend will automatica
### Error Handling
- `status: "Fail"`: video generation failed; explain to the user
- `success: false` + `error: "No matching provider found"`: MiniMax Media Provider is not configured
- `success: false` + `error: "No matching provider found"`: No enabled MiniMax provider with `video_gen` service found
- `success: false` + `error: "API Key not configured"`: API Key has not been entered
- **Insufficient quota** (errors related to `statusCode: 429`, `insufficient_quota`, `balance`): text-to-video cannot fall back (the Fast model does not support T2V); inform the user of insufficient quota; image-to-video can switch to `MiniMax-Hailuo-2.3-fast` and retry from Step 1
- Polling exceeds 10 minutes without completion: inform the user that the task may have timed out