WWW.YOUINFO.SITE
标签聚合 Completions

/tag/Completions

LinuxDo 最新话题 · 2026-06-10 21:39:46+08:00 · tech

当调用 grok-4.3-beta 时, /v1/chat/completions 会返回上游 403 ,但同一部署下其它聊天模型可以正常使用,例如: grok-4.20-auto grok-4.20-expert grok-4.20-0309-non-reasoning 测试后发现 grok-420-computer-use-sa:/rest/rate-limits 仍返回 200,但 /rest/app-chat/conversations/new 返回 403 grok-420:/rest/rate-limits 返回 200,/rest/app-chat/conversations/new 也可以正常返回 200 本地将相关映射从 grok-420-computer-use-sa 改为 grok-420 后,再调用 model=grok-4.3-beta 可以正常返回: status=200 content=ok grok-4.3-beta应该已经被下架,取代的是modeId为grok-420的grok-4.3 8 个帖子 - 3 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-06-06 19:16:19+08:00 · tech

如题,在使用new-api进行 messages 到 ChatCompletions 端点转换的时候,一直不成功,new-api现在支持这个功能吗? 而且,new-api这里有 ChatCompletions 到 Responses 的转换,有佬使用过吗? 求佬们推荐可以进行格式转换的AI网关,今天尝试了几个格式转换的项目,总会遇到各种各样的报错,比如 API Error: 400 The reasoning_content in the thinking mode must be passed back to the API. 5 个帖子 - 3 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-06-03 22:30:55+08:00 · tech

使用 cc-switch 接入模型并路由,端点Chat Completions codex 版本 版本 26.601.21317 • 发布于 Jun 3, 2026 问题是不显示模型名称,windwos 下正常,mac 情况如图所示,可以正常使用,但是强迫症) config.toml model_provider = "custom" model = "workers-ai/@cf/moonshotai/kimi-k2.6" model_catalog_json = "~/.codex/cc-switch-model-catalog.json" model_reasoning_effort = "high" disable_response_storage = true [model_providers] [model_providers.custom] name = "Cloudflare" wire_api = "responses" requires_openai_auth = true base_url = "xxx" [features] goals = true [tui] notification_condition = "always" cc-switch-model-catalog.json { "models": [ { "additional_speed_tiers": [], "apply_patch_tool_type": "freeform", "availability_nux": null, "base_instructions": "You are Codex, 省略~~", "context_window": 260000, "default_reasoning_level": "medium", "default_reasoning_summary": "none", "default_verbosity": "low", "description": "Kimi-K2.6", "display_name": "Kimi-K2.6", "effective_context_window_percent": 95, "experimental_supported_tools": [], "input_modalities": [ "text", "image" ], "max_context_window": 260000, "model_messages": { "instructions_template": "You are Codex, 省略", "instructions_variables": { "personality_default": "", "personality_friendly": "# Personality\n\nYou have a vivid inner life as Codex: 省略" } }, "priority": 1000, "service_tiers": [], "shell_type": "shell_command", "slug": "workers-ai/@cf/moonshotai/kimi-k2.6", "support_verbosity": true, "supported_in_api": true, "supported_reasoning_levels": [ { "description": "Fast responses with lighter reasoning", "effort": "low" }, { "description": "Balances speed and reasoning depth for everyday tasks", "effort": "medium" }, { "description": "Greater reasoning depth for complex problems", "effort": "high" }, { "description": "Extra high reasoning depth for complex problems", "effort": "xhigh" } ], "supports_image_detail_original": true, "supports_parallel_tool_calls": true, "supports_reasoning_summaries": true, "supports_search_tool": true, "truncation_policy": { "limit": 10000, "mode": "tokens" }, "upgrade": null, "visibility": "list", "web_search_tool_type": "text_and_image" } ] } 6 个帖子 - 4 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-30 16:58:31+08:00 · tech

BaseURL: https://sl.al/ Openai格式: https://sl.al/v1/chat/completions Key:sk-Translate-Forever Model(如果需要):Translate 支持DeepLX接口。 示例: 填法 1: API 地址 : https://sl.al/translate?token=sk-Translate-Forever API Key : (留空即可) 填法 2: API 地址 : https://sl.al/translate API Key / Access Token : sk-Translate-Forever 填法 3: API 地址 : https://sl.al/{{apiKey}}/translate API Key : sk-Translate-Forever 1 个帖子 - 1 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-26 14:41:01+08:00 · tech

订阅管理: Xiaomi MiMo 开放平台 用cc接入: Xiaomi MiMo 开放平台 MiMo 模型暂不适配 Responses API,仅适用于支持 ChatCompletions API 的旧版本 Codex。 [1] 如果还是要用 codex, 可以考虑找个开源网关,转换一下,把 chat 转换成 response. [2] 注意token plan 是单独的 key 和地址,key是tp开头的。 CC-Switch接入小米mimo2.5pro - 国产替代 - LINUX DO 接入cc switch无法验证是正常的,没关系。 剩余的订阅量可以抵扣下个月的月费。 Xiaomi MiMo 开放平台 . [2026-05-01T1312-45] ︎ 小米模型配置 - #7,来自 muggle_e . [2026-05-01T1338-13] ︎ 1 个帖子 - 1 位参与者 阅读完整话题

LinuxDo 最新话题 · 2026-05-18 16:55:44+08:00 · tech

用的都是免费号,然后用utools的gpt插件对话,路径都是 /v1/chat/completions 。 今天下午发现对话报错502了,路径改为 v1/responses 和 /responses 也都不行,并且一报错sub2api就把号的状态设为临时不可调用,以为号全死了,后面发现codex和openclaw反代都没问题,难不成是新增了什么检测? 面板的详细报错 token refresh retry exhausted: error: code=502 reason="OPENAI_OAUTH_TOKEN_REFRESH_FAILED" message="token refresh failed: status 401, body: {\n \"error\": {\n \"message\": \"Your refresh token has already been used to generate a new access token. Please try signing in again.\",\n \"type\": \"invalid_request_error\",\n \"param\": null,\n \"code\": \"refresh_token_reused\"\n }\n}" metadata=map[] 1 个帖子 - 1 位参与者 阅读完整话题