copilot-custom-endpoint 1.7.4 → 1.7.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/example-config.md +0 -17
- package/docs/models/minimax.md +21 -43
- package/docs/pricing.md +6 -7
- package/package.json +1 -1
package/docs/example-config.md
CHANGED
|
@@ -124,23 +124,6 @@ Here's a complete, real-world `chatLanguageModels.json` that combines **the `cus
|
|
|
124
124
|
"temperature": 1,
|
|
125
125
|
"top_p": 0.95
|
|
126
126
|
}
|
|
127
|
-
},
|
|
128
|
-
{
|
|
129
|
-
"id": "MiniMax-M3-Priority",
|
|
130
|
-
"name": "MiniMax M3 (Priority)",
|
|
131
|
-
"url": "https://api.minimax.io/v1/chat/completions",
|
|
132
|
-
"toolCalling": true,
|
|
133
|
-
"vision": true,
|
|
134
|
-
"streaming": true,
|
|
135
|
-
"maxInputTokens": 1048576,
|
|
136
|
-
"maxOutputTokens": 131072,
|
|
137
|
-
"requestBody": {
|
|
138
|
-
"thinking": { "type": "adaptive" },
|
|
139
|
-
"reasoning_split": true,
|
|
140
|
-
"temperature": 1,
|
|
141
|
-
"top_p": 0.95,
|
|
142
|
-
"service_tier": "priority"
|
|
143
|
-
}
|
|
144
127
|
}
|
|
145
128
|
]
|
|
146
129
|
},
|
package/docs/models/minimax.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> **TL;DR:** MiniMax-M3 works directly — no proxy needed. Use `thinking: { type: "adaptive" }` + `reasoning_split: true` in `requestBody` so the model can reason and the response arrives in a clean OpenAI format (`reasoning_details` field, separate from `content`). **Important:** `thinking: { type: "disabled" }` is **not** a hard override — the model still reasons internally and emits `<think>` tags / `reasoning_content` regardless.
|
|
4
4
|
>
|
|
5
|
-
> Want faster responses and fewer admission failures during peak hours? Add `"service_tier": "priority"` to
|
|
5
|
+
> Want faster responses and fewer admission failures during peak hours? Add `"service_tier": "priority"` to the single `MiniMax-M3` entry's `requestBody` — same model, **1.5× cost** for **priority admission**. (You can only toggle `service_tier` on the existing entry; registering a second picker entry with a different `id` is not valid on the custom-endpoint path because VS Code forwards the `id` as the upstream `model` parameter.) See [M3 Priority tier](#4-m3-priority-tier-optional) below.
|
|
6
6
|
>
|
|
7
7
|
> The same `url`, `model id`, and `requestBody` work for **both** Pay-as-You-Go (account-balance billing) and Token Plan (monthly/annual subscription) — only the API key in the secret field changes.
|
|
8
8
|
>
|
|
@@ -124,55 +124,33 @@ When the Token Plan 5-hour or weekly quota is exhausted, the request fails with
|
|
|
124
124
|
|
|
125
125
|
MiniMax exposes M3 with a per-request **`service_tier`** switch that promotes the request into MiniMax's priority admission queue. Priority is **not** a separate model — it is the same `MiniMax-M3` weights invoked with `"service_tier": "priority"` in the request body, costing **1.5× Standard** in exchange for **priority admission** (faster responses, fewer failures during MiniMax peak hours — typically 15:00–17:30 weekdays). Capabilities, context window (1M, guaranteed 512K), vision, tool calling, rate limits (200 RPM / 10M TPM), and thinking modes are identical to Standard.
|
|
126
126
|
|
|
127
|
-
|
|
127
|
+
**You can only toggle `service_tier` by editing the single `MiniMax-M3` entry.** VS Code's built-in custom-endpoint handler forwards the model block's `id` field as the upstream `model` parameter, and `MiniMax-M3` is the only valid MiniMax M3 model id on the upstream API. Adding a second model block with a different `id` (such as `MiniMax-M3-Priority`) is **not valid** — the upstream API will reject the unknown model. Duplicating the `MiniMax-M3` id twice is also invalid and causes VS Code picker bugs.
|
|
128
|
+
|
|
129
|
+
To switch the existing entry from Standard to Priority, add one line to `requestBody`:
|
|
128
130
|
|
|
129
131
|
```json
|
|
130
132
|
{
|
|
131
|
-
"
|
|
132
|
-
"
|
|
133
|
-
"
|
|
134
|
-
"
|
|
135
|
-
"
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
"thinking": { "type": "adaptive" },
|
|
147
|
-
"reasoning_split": true,
|
|
148
|
-
"temperature": 1,
|
|
149
|
-
"top_p": 0.95
|
|
150
|
-
}
|
|
151
|
-
},
|
|
152
|
-
{
|
|
153
|
-
"id": "MiniMax-M3-Priority",
|
|
154
|
-
"name": "MiniMax M3 (Priority)",
|
|
155
|
-
"url": "https://api.minimax.io/v1/chat/completions",
|
|
156
|
-
"toolCalling": true,
|
|
157
|
-
"vision": true,
|
|
158
|
-
"streaming": true,
|
|
159
|
-
"maxInputTokens": 1048576,
|
|
160
|
-
"maxOutputTokens": 131072,
|
|
161
|
-
"requestBody": {
|
|
162
|
-
"thinking": { "type": "adaptive" },
|
|
163
|
-
"reasoning_split": true,
|
|
164
|
-
"temperature": 1,
|
|
165
|
-
"top_p": 0.95,
|
|
166
|
-
"service_tier": "priority"
|
|
167
|
-
}
|
|
168
|
-
}
|
|
169
|
-
]
|
|
133
|
+
"id": "MiniMax-M3",
|
|
134
|
+
"name": "MiniMax M3 (Priority)",
|
|
135
|
+
"url": "https://api.minimax.io/v1/chat/completions",
|
|
136
|
+
"toolCalling": true,
|
|
137
|
+
"vision": true,
|
|
138
|
+
"streaming": true,
|
|
139
|
+
"maxInputTokens": 1048576,
|
|
140
|
+
"maxOutputTokens": 131072,
|
|
141
|
+
"requestBody": {
|
|
142
|
+
"thinking": { "type": "adaptive" },
|
|
143
|
+
"reasoning_split": true,
|
|
144
|
+
"temperature": 1,
|
|
145
|
+
"top_p": 0.95,
|
|
146
|
+
"service_tier": "priority"
|
|
147
|
+
}
|
|
170
148
|
}
|
|
171
149
|
```
|
|
172
150
|
|
|
173
|
-
|
|
151
|
+
To go back to Standard, remove the `"service_tier": "priority"` line (the API default is `standard`). The `name` field is a local VS Code picker label, so it can be changed freely to reflect the current tier.
|
|
174
152
|
|
|
175
|
-
> The `
|
|
153
|
+
> The `service_tier` parameter is supported on **both** the OpenAI-compatible and Anthropic-compatible endpoints. The third-party `klarkxy/minimax-vscode` extension surfaces the Standard/Priority toggle as a separate picker entry because it is a native `LanguageModelChatProvider` that hard-codes the upstream model id internally and rewrites the picker id — that override mechanism is not available to the built-in custom-endpoint path.
|
|
176
154
|
|
|
177
155
|
For the full breakdown (effective pricing, session cost, when Priority is worth the 50% premium), see [docs/research/minimax-m3-priority.md](../research/minimax-m3-priority.md).
|
|
178
156
|
|
package/docs/pricing.md
CHANGED
|
@@ -58,7 +58,7 @@ All models are listed together below, sorted by Cost per intelligence ascending
|
|
|
58
58
|
|
|
59
59
|
⁴ GLM 5.2 is Z.ai's newly released flagship model (Opus-level intelligence / 1M Solid context). AA Intelligence Index score (**51.0**) and pricing of **$1.40** (input), **$0.26** (cached), and **$4.40** (output) per 1M tokens confirmed on its [model page](https://artificialanalysis.ai/models/glm-5-2). Session cost is identical to GLM 5.1 (~$1.14).
|
|
60
60
|
|
|
61
|
-
⁵ **MiniMax M3 Priority** is not a separate model — it is the same `MiniMax-M3` weights invoked with `"service_tier": "priority"` in the request body. Priority costs **1.5× Standard** across input, output, and cache reads (list prices shown above; effective rates after the standing 50% off are $0.45/$1.80/$0.09 ≤512K and $0.90/$3.60/$0.18 >512K), in exchange for **priority admission** (faster responses, fewer failures during MiniMax peak hours — typically 15:00–17:30 weekdays). Capabilities, context window (1M, guaranteed 512K), vision, tool calling, rate limits (200 RPM / 10M TPM), and thinking modes are identical to Standard. To enable it on
|
|
61
|
+
⁵ **MiniMax M3 Priority** is not a separate model — it is the same `MiniMax-M3` weights invoked with `"service_tier": "priority"` in the request body. Priority costs **1.5× Standard** across input, output, and cache reads (list prices shown above; effective rates after the standing 50% off are $0.45/$1.80/$0.09 ≤512K and $0.90/$3.60/$0.18 >512K), in exchange for **priority admission** (faster responses, fewer failures during MiniMax peak hours — typically 15:00–17:30 weekdays). Capabilities, context window (1M, guaranteed 512K), vision, tool calling, rate limits (200 RPM / 10M TPM), and thinking modes are identical to Standard. To enable it on the custom-endpoint entry, add `"service_tier": "priority"` to the `requestBody` of the single `MiniMax-M3` block (and remove it to go back to Standard). See [docs/models/minimax.md](models/minimax.md#4-m3-priority-tier-optional) and [docs/research/minimax-m3-priority.md](research/minimax-m3-priority.md) for the full breakdown.
|
|
62
62
|
|
|
63
63
|
⁶ **Claude Sonnet 5** has introductory pricing of **$2.00 / $0.20 / $10.00** (input / cached / output) through **August 31, 2026**, after which the standard pricing of $3.00 / $0.30 / $15.00 shown above takes effect. See [Anthropic's pricing page](https://claude.com/pricing) for the latest.
|
|
64
64
|
|
|
@@ -76,12 +76,11 @@ Cost per intelligence = estimated session cost ÷ Intelligence Index score. Sess
|
|
|
76
76
|
> - **Kimi K2.6** pricing is from the **Moonshot platform** (direct). Via DashScope: $0.89 input / $3.71 output.
|
|
77
77
|
> - **DashScope** offers a **free quota** of 1M input + 1M output tokens per model, valid for 90 days.
|
|
78
78
|
> - **MiniMax M3** uses **tiered pricing** — input price doubles above 512K input tokens. Cache hits are priced at 20% of the input rate ($0.12/M ≤512K, $0.24/M >512K). A **permanent 50% off** discount applies to all MiniMax-M3 pay-as-you-go usage (Standard and Priority tiers), making the effective rates half the list prices above.
|
|
79
|
-
|
|
80
|
-
- **
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
> - For typical Copilot chat usage (short-to-medium prompts), you'll almost always fall in the lowest pricing tier.
|
|
79
|
+
> - **MiniMax M3 Priority** is not a separate model — it is the same `MiniMax-M3` weights invoked with `"service_tier": "priority"` in the request body. Priority costs **1.5× Standard** across input, output, and cache reads, in exchange for **priority admission** (faster responses, fewer failures during MiniMax peak hours — typically 15:00–17:30 weekdays). Capabilities, context window (1M, guaranteed 512K), vision, tool calling, rate limits (200 RPM / 10M TPM), and thinking modes are identical to Standard. See [docs/research/minimax-m3-priority.md](research/minimax-m3-priority.md) for the full breakdown.
|
|
80
|
+
> - **GLM** models support prompt caching — cache hits are priced at $0.24/M for 5V Turbo and $0.26/M for 5.1.
|
|
81
|
+
> - **MiMo** offers a **Token Plan** subscription model with discounted rates and a free cache-writing promotion.
|
|
82
|
+
> - **MAI-Code-1-Flash** is a continuously improving model — performance and behavior may evolve over time as new checkpoints are released.
|
|
83
|
+
> - For typical Copilot chat usage (short-to-medium prompts), you'll almost always fall in the lowest pricing tier.
|
|
85
84
|
|
|
86
85
|
> **How long does 7,000 credits last?** A Pro+ subscriber running 50-turn sessions could afford roughly **13 GPT-5.5 sessions**, **23 Opus sessions**, or **212 Raptor mini sessions** per month — or mix and match. (Multiply session cost by 100 to convert to AI credits.)
|
|
87
86
|
|