MINIMAX IN TELEGRAM · PRO FLAGSHIP
VUST runs MiniMax M3 as a Pro-plan flagship in @vustbot. You pick it by its full name — VUST MiniMax — MiniMax M3 — and the bot never silently answers with another model.
MiniMax M3
Usually fits
Analysis · Coding · Long documents
Pro and Max plans, inside the included allowance. Outside a plan the bot shows the exact one-shot Balance option before anything runs.
Reply up to 3,000 tokens
Every run re-checks access, limits and BalanceDirect answer
Reach for it on structured analysis, multi-file coding and work that has to hold a lot of context at once — and when you want this specific model's take. For everyday drafts an included Core model is usually enough; the catalog keeps both one tap apart.
What @vustbot does in each access outcome after you send a task to VUST MiniMax — MiniMax M3. Explained here, decided in Telegram; paraphrased, not interactive.
Outcome
What the bot offers
What stays true
Confirms “VUST MiniMax — MiniMax M3” and runs the task inside the included allowance.
The reply is labeled with the model that produced it.
Shows Pro/Max plans, the exact one-shot Balance price for this run, and an explicit switch back to your previous available model.
Your prompt is preserved. Nothing is charged before you confirm.
Offers to run it as an exact one-shot Balance option, wait for the allowance to reset, or pick an included model explicitly.
Applies on Pro and Max too — flagship allowances are bounded and re-checked per run.
The run fails visibly and nothing is charged — send the task again or pick another model explicitly.
VUST does not silently answer with a different model.
Always true
Model named in full before the run · prompt preserved on plan or allowance denial · nothing charged on a failed run · no silent model switch.
Comparison basis
The model name is shown as marketed by the vendor. VUST availability, plan and limits come from the runtime catalog, checked 2026-07-26; third-party release claims are deliberately omitted until primary sources are attached. VUST claims neither partnership nor universal model superiority.
Unless a separate method is stated above, this page does not claim a head-to-head product-quality benchmark.
Checked: 2026-07-26
Supported model
Vendor naming
MiniMax M3
In VUST
The single MiniMax entry VUST supports today
Status
1 model
Model naming
Vendor naming
MiniMax M3
In VUST
VUST MiniMax — MiniMax M3
Status
Named before every run
Plans and access
Vendor naming
Not applicable
In VUST
Pro and Max; outside a plan, an exact one-shot Balance option before the run
Status
Re-checked per run
Context and reply
Vendor naming
Not restated here
In VUST
Compact text context; reply capped at 3000 tokens
Status
Product-bounded
If unavailable
Vendor naming
Not applicable
In VUST
The run fails visibly and nothing is charged; send the task again — no silent switch
Status
Honest failure
Citable summary (checked 2026-07-26): VUST offers MiniMax M3 as a Pro-plan flagship text model in @vustbot, selected by its full name with a direct Telegram link. Every run re-checks plan, included limits and Balance; a plan or allowance denial preserves the prompt, a temporary failure charges nothing, and VUST never silently substitutes another model.Open VUST MiniMax — MiniMax M3
Yes, as an exact one-shot Balance run: the bot shows the price before you confirm, keeps your prompt, and charges only after a successful reply.
The direct link selects MiniMax M3: it opens @vustbot with the model already selected, before you send your task. It is this exact model, not a generic entry point into the bot, and you still send the prompt yourself — nothing runs on its own.
No. You select the model inside Telegram and VUST shows its full name before the run. There is no model download, no API key and no separate cloud console.
It can. Auto may select MiniMax M3 when it fits the task, your plan, current access and availability — most often for analysis, coding or long-document work on Pro/Max. Pick it manually to pin MiniMax M3 for your next request instead. Either way, VUST never silently substitutes a different model — the reply is always labeled.