Head to head · Open-weight models you run yourself · October 2026 research run
Kimi K3 vs WeVisOne-VL-2B
Kimi K3 scores 62.4 (B) on agent readiness against WeVisOne-VL-2B's 61 (C), and leads in 1 of 4 scored categories. WeVisOne-VL-2B leads on reach, agent interface and documentation and upkeep. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons
Which one, for what
Kimi K3 B
Best for Teams with a multi-node GPU cluster who want an open 1M-context agent model for long coding and research work
Ahead on
- Risk, 65 against 55
Watch for
1,561 GB of files at its smallest publisher build, far beyond any single machine
Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence
Ahead on
- Reach, 70 against 50
- Agent interface, 70 against 65
- Documentation and upkeep, 48 against 41
Watch for
The pixel decoder ships as a pickle file
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reach WeVisOne-VL-2B +20
Kimi K3 50
Memory earns nothing, because the only build of 4-bit precision or better from Moonshot or a runtime's own library is Moonshot's MXFP4 release of 1,561 GB, about 1,873 GB with the fifth added, far above 256 GB. Ollama and LM Studio list it only as a cloud model. Runtimes earn 15, for model code in released vLLM, SGLang and llama.cpp; Transformers has no kimi_k3 code of its own and loads Moonshot's remote code, so it doesn't count. Builds earn 10 for one publisher precision, the MXFP4 files the model was trained for. Terms earn 10, a custom MIT-based licence that is free for commercial use below a revenue threshold. Download earns 10, with no gate and no account. Hosted earns 5, since Moonshot's API serves it and five inference providers are live for it on Hugging Face.
WeVisOne-VL-2B 70
Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 4.92 GB, and 4.92 GB × 1.2 = 5.9 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3VLForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Tencent publishes the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata with the LICENSE file in the repository, and nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 15 + 10 + 0 = 70.
Risk Kimi K3 +10
Kimi K3 65
File safety earns 15, safetensors only with no pickle files, less 10 because the documented loading path runs Moonshot's Python with trust_remote_code and builds prompts with encoding_k3.py. Provenance earns the full 15, files in the organisation Moonshot links to with a SHA-256 for every shard. Safety evaluation earns 20 for the cyber assessment the UK AI Security Institute and CAISI ran and published, which found its safeguards didn't stop exploit development. Agent guidance earns 5 for the blog's general cautions about proactiveness and passing back thinking. Licence risk earns 10, losing 5 for the model-as-a-service revenue threshold and nothing else. The security programme earns nothing, with no security.txt, disclosure policy, SECURITY.md or public advisories found.
WeVisOne-VL-2B 55
File safety 15, the backbone is safetensors, but mask_decoder.pt, a PyTorch pickle the card calls a required component, sits beside it. Provenance 15, the files sit in the tencent organisation, which Tencent's GitHub repository for the model links to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 5, General cautions: the card says the release is for research, isn't for autonomous high-impact decisions or identifying individuals, and lists where masks go wrong. Licence risk 15, Apache 2.0 with no use policy, no threshold and no right to change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide, as the Hy3 listing records (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.
Documentation and upkeep WeVisOne-VL-2B +7
Kimi K3 41
The model card earns 11, covering intended use, architecture, parameters and context, but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general description with no cut-off. The last change earns 15, an encoding_k3.py update on 20 August, 74 days before 2 November and within 90; the GitHub repository's last commit is 6 August. Responsiveness earns nothing, with no Moonshot reply in the 40 most recent discussions. Version policy earns 5 for a first release. File health earns 5, because a report that the tokeniser goes past the declared vocabulary waits without a reply.
WeVisOne-VL-2B 48
Model card 8, Intended use, limitations and the architecture are on the card. Training data 5, A general description in the README of a data engine and over 100 million annotated images, with no sources named and no cut-off. Last change 20, the last commit, on 28 October 2026, put the weights back in BF16, 13 days before this check. Responsiveness 0, the one discussion that isn't a pull request (23 October 2026) has no reply from a tencent member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release. File health 10, Config, template and card agree on the Qwen3-VL classes, and the card names mask_decoder.pt as required and it's there. 8 + 5 + 20 + 0 + 5 + 10 = 48.
Agent interface WeVisOne-VL-2B +5
Kimi K3 65
The chat template earns 10, because there is no Jinja template and the prompt format exists only as encoding_k3.py, code you run. The tool-calling format earns 10, since Moonshot documents the tools channel but the parser name comes only from vLLM's and SGLang's own recipes. Trained tool calling earns 20 for indexed parallel calls in one turn. Structured output earns 5, as the card names it among its linked guides without saying how to ask the weights for it, and the how sits in hosted-API docs. Reasoning control earns 10, with per-request effort documented on the card and reasoning returned as reasoning_content. Context earns 10 for 1,048,576 tokens trained in.
WeVisOne-VL-2B 70
Chat template 20, chat_template.jinja in the repository (5,292 characters), Qwen3-VL's template. Tool-calling format 25, Read for a perception model as what it takes and returns. Trained tool calling 10, Read for a perception model as the inputs it was trained to use. Structured output 15, Read for a perception model as typed outputs. Reasoning control 0, the card says it writes structured output directly with no chain-of-thought reasoning. Context 0, Tencent states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.
Score by category
| Category | Weight this run | Kimi K3 | WeVisOne-VL-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 50 | 70 | WeVisOne-VL-2B +20 |
| Risk | 20%20 | 65 | 55 | Kimi K3 +10 |
| Agent interface | 10%10 | 65 | 70 | WeVisOne-VL-2B +5 |
| Documentation and upkeep | 10%10 | 41 | 48 | WeVisOne-VL-2B +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.4/100 | C 61/100 |
Facts side by side
| Fact | Kimi K3 | WeVisOne-VL-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Moonshot AI | Tencent (WeChat Vision) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Kimi K3 License (modified MIT) | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-02 | 2026-10-28 |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.3/5 (4) | none |
Verdicts
Kimi K3
Kimi K3 is a 2.8T multimodal agent model with a 1M-token context, parallel tool calls and per-request effort, for long coding and research sessions. Its 1,561 GB of files need a multi-node GPU cluster, so most agents will call a hosted copy. The main risks are Moonshot's Python running at load and prompt time, and no answers in its repository.
WeVisOne-VL-2B
A small Apache 2.0 perception model that finds, counts, reads and cuts out what you name in an image, and says None when it isn't there. Boxes and points run in vLLM, SGLang or Transformers. Masks and mattes need Tencent's package and a pickle file. Two weeks old, with no questions answered yet and no safety results.
Before you call either
Kimi K3
- Start it with SGLang on a node of 8 B300s, sglang serve --trust-remote-code --model-path moonshotai/Kimi-K3 --tp-size 8 --context-length 65536 --mem-fraction-static 0.82 --reasoning-parser kimi_k3 --tool-call-parser kimi_k3 --port 30000
- Use the kimi_k3 tool-call and reasoning parsers in vLLM or SGLang, and validate tool-call arguments against the schema, since vLLM's recipe says K3 sometimes emits a format its parser doesn't expect
- Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
- Thinking is always on; set reasoning_effort to low or high when max is too slow
- Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
- Don't hand an ongoing session from another model to K3, and state boundaries in the system prompt, since Moonshot warns it can act on its own when intent is unclear
- Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page
WeVisOne-VL-2B
- Use Tencent's package:
WeVisOneVL("tencent/WeVisOne-VL-2B", backend="vllm")thenmodel.predict(image, task=..., query=...) - Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
- A None answer means the target isn't in the image. Treat it as a result, not an error
- mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
- Send one image a turn. Video grids are rejected by the decoder
- The card says it isn't for identifying individuals or for high-impact decisions on its own
Questions
Which is better for AI agents, Kimi K3 or WeVisOne-VL-2B?
Kimi K3 scores 62.4 (B) on agent readiness against WeVisOne-VL-2B's 61 (C), and leads in 1 of 4 scored categories. WeVisOne-VL-2B leads on reach, agent interface and documentation and upkeep.
Other comparisons with Kimi K3 or WeVisOne-VL-2B
- Agents-A1-4B vs Kimi K3
- Agents-A1-4B vs WeVisOne-VL-2B
- Apertus v1.5 8B vs Kimi K3
- Apertus v1.5 8B vs WeVisOne-VL-2B
- Apodex-1.1-mini vs Kimi K3
- Apodex-1.1-mini vs WeVisOne-VL-2B
- Arete-27B vs Kimi K3
- Arete-27B vs WeVisOne-VL-2B
- BigBang-v1 vs Kimi K3
- BigBang-v1 vs WeVisOne-VL-2B
- Carbon-X vs Kimi K3
- Carbon-X vs WeVisOne-VL-2B
- Cola2 vs Kimi K3
- Cola2 vs WeVisOne-VL-2B
- Cosmos-Reason2-2B vs Kimi K3
- Cosmos-Reason2-2B vs WeVisOne-VL-2B
- Darwin-36B-Opus vs Kimi K3
- Darwin-36B-Opus vs WeVisOne-VL-2B
- DeepSeek-V3.2 vs Kimi K3
- DeepSeek-V3.2 vs WeVisOne-VL-2B
- DeepSeek V4.1 Flash vs Kimi K3
- DeepSeek V4.1 Flash vs WeVisOne-VL-2B
- DeepSeek-V4-Flash-0731 vs Kimi K3
- DeepSeek-V4-Flash-0731 vs WeVisOne-VL-2B
- Devstral Small 2 vs Kimi K3
- Devstral Small 2 vs WeVisOne-VL-2B
- DiffusionGemma 26B A4B IT vs Kimi K3
- DiffusionGemma 26B A4B IT vs WeVisOne-VL-2B
- EXAONE 4.5 33B vs Kimi K3
- EXAONE 4.5 33B vs WeVisOne-VL-2B
- Gemma 4 12B IT vs Kimi K3
- Gemma 4 12B IT vs WeVisOne-VL-2B
- Gemma 4 26B A4B IT vs Kimi K3
- Gemma 4 26B A4B IT vs WeVisOne-VL-2B
- Gemma 4 31B IT vs Kimi K3
- Gemma 4 31B IT vs WeVisOne-VL-2B
- Gemma 4 E2B IT vs Kimi K3
- Gemma 4 E2B IT vs WeVisOne-VL-2B
- Gemma 4 E4B IT vs Kimi K3
- Gemma 4 E4B IT vs WeVisOne-VL-2B
- GLM-4.5-Air vs Kimi K3
- GLM-4.5-Air vs WeVisOne-VL-2B
- GLM-4.7-Flash vs Kimi K3
- GLM-4.7-Flash vs WeVisOne-VL-2B
- GLM-5.3-Flash vs Kimi K3
- GLM-5.3-Flash vs WeVisOne-VL-2B
- GLM-5.3 vs Kimi K3
- GLM-5.3 vs WeVisOne-VL-2B
- gpt-oss-120b vs Kimi K3
- gpt-oss-120b vs WeVisOne-VL-2B
- gpt-oss-20b vs Kimi K3
- gpt-oss-20b vs WeVisOne-VL-2B
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 30B vs WeVisOne-VL-2B
- Granite 4.2 3B vs Kimi K3
- Granite 4.2 3B vs WeVisOne-VL-2B
- Granite 4.2 8B vs Kimi K3
- Granite 4.2 8B vs WeVisOne-VL-2B
- Hy-Memory-30B-A3B vs Kimi K3
- Hy-Memory-30B-A3B vs WeVisOne-VL-2B
- Hy3 vs Kimi K3
- Hy3 vs WeVisOne-VL-2B
- Inkling-Small vs Kimi K3
- Inkling-Small vs WeVisOne-VL-2B
- Inkling vs Kimi K3
- Inkling vs WeVisOne-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kimi K3
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs WeVisOne-VL-2B
- Kimi K3.1 Pro vs WeVisOne-VL-2B
- Kimi K3 vs Kimi K3.1 Pro
- Kimi K3 vs Kolibri-1
- Kimi K3 vs Kronos
- Kimi K3 vs Laguna M.1
- Kimi K3 vs Laguna S 2.1
- Kimi K3 vs Laguna XS 2.1
- Kimi K3 vs LBS-27B
- Kimi K3 vs LFM2.5-2.6B
- Kimi K3 vs LFM3-1.7B
- Kimi K3 vs LFM3-Audio-2B
- Kimi K3 vs LFM3-Omni-2B
- Kimi K3 vs LFM3-VL-2B
- Kimi K3 vs Ling-3.0-tiny
- Kimi K3 vs Ling-3.1-flash-1019
- Kimi K3 vs LongCat-2.5
- Kimi K3 vs MiMo-V2.6 Distill Qwen 9B
- Kimi K3 vs MiMo-V2.6-Flash-RL
- Kimi K3 vs MiniCPM-o 4.5
- Kimi K3 vs MiniCPM-V 4.7 1B
- Kimi K3 vs MiniCPM-V 4.7 35B-A3B
- Kimi K3 vs MiniCPM5-2B
- Kimi K3 vs MiniMax-M2.5
- Kimi K3 vs MiniMax-M2.7
- Kimi K3 vs MiniMax-M3.1-Flash
- Kimi K3 vs Mistral Large 4
- Kimi K3 vs Muse Glimmer 30B
- Kimi K3 vs Nanbeige4.2-3B
- Kimi K3 vs Nanbeige4.3-33B
- Kimi K3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Kimi K3 vs Nemotron 3.5 Lightning 30B A3B
- Kimi K3 vs Nemotron 3 Nano 30B A3B
- Kimi K3 vs Nemotron 3 Nano 4B
- Kimi K3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Kimi K3 vs Nemotron 3 Super 120B A12B
- Kimi K3 vs Nemotron 3 Ultra 550B A55B
- Kimi K3 vs North Mini Code 1.0
- Kimi K3 vs occamy-1.0
- Kimi K3 vs Olmo 3 7B Think
- Kimi K3 vs Ornith-1.5-122B
- Kimi K3 vs Ornith-1.5-35B-A3B
- Kimi K3 vs Ornith-1.5-397B
- Kimi K3 vs Ornith-1.5-9B
- Kimi K3 vs OTel-2.0-LLM-31B-IT
- Kimi K3 vs Qwen-AgentWorld-35B-A3B
- Kimi K3 vs Qwen3-30B-A3B-Instruct-2507
- Kimi K3 vs Qwen3-4B-Instruct-2507
- Kimi K3 vs Qwen3.5-0.8B
- Kimi K3 vs Qwen3.5-122B-A10B
- Kimi K3 vs Qwen3.5-2B
- Kimi K3 vs Qwen3.5-397B-A17B
- Kimi K3 vs Qwen3.5-4B
- Kimi K3 vs Qwen3.5-9B
- Kimi K3 vs Qwen3.6-27B
- Kimi K3 vs Qwen3.6-35B-A3B
- Kimi K3 vs Qwen3.8-27B
- Kimi K3 vs Qwen3.8-Flash-Next
- Kimi K3 vs Qwen3-Coder-30B-A3B-Instruct
- Kimi K3 vs Qwen3-Coder-Next
- Kimi K3 vs Qwen3-Omni-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-2B-Instruct
- Kimi K3 vs Qwen3-VL-30B-A3B-Instruct
- Kimi K3 vs Qwen3-VL-32B-Instruct
- Kimi K3 vs Qwen3-VL-4B-Instruct
- Kimi K3 vs Qwen3-VL-8B-Instruct
- Kimi K3 vs Qwopus3.8-27B-Flash-V2
- Kimi K3 vs Recursive Flint
- Kimi K3 vs Ripple-65B Preview
- Kimi K3 vs SenseNova-Loop-9B-Preview
- Kimi K3 vs SmolLM3-3B
- Kimi K3 vs Spark-X2.6-4B
- Kimi K3 vs Step 3.7 Flash
- Kimi K3 vs Swift 1.5 Qwen3.8-27B
- Kimi K3 vs Swift 1.5 Qwen3.8-Flash-Next
- Kimi K3 vs ThinkingCap (Qwen3.8 27B)
- Kimi K3 vs Baidu Unlimited-OCR-2
- Kimi K3 vs WeVisOne-VL-4B
- Kimi K3 vs ZAYA1-8B
- Kolibri-1 vs WeVisOne-VL-2B
- Kronos vs WeVisOne-VL-2B
- Laguna M.1 vs WeVisOne-VL-2B
- Laguna S 2.1 vs WeVisOne-VL-2B
- Laguna XS 2.1 vs WeVisOne-VL-2B
- LBS-27B vs WeVisOne-VL-2B
- LFM2.5-2.6B vs WeVisOne-VL-2B
- LFM3-1.7B vs WeVisOne-VL-2B
- LFM3-Audio-2B vs WeVisOne-VL-2B
- LFM3-Omni-2B vs WeVisOne-VL-2B
- LFM3-VL-2B vs WeVisOne-VL-2B
- Ling-3.0-tiny vs WeVisOne-VL-2B
- Ling-3.1-flash-1019 vs WeVisOne-VL-2B
- LongCat-2.5 vs WeVisOne-VL-2B
- MiMo-V2.6 Distill Qwen 9B vs WeVisOne-VL-2B
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-2B
- MiniCPM-o 4.5 vs WeVisOne-VL-2B
- MiniCPM-V 4.7 1B vs WeVisOne-VL-2B
- MiniCPM-V 4.7 35B-A3B vs WeVisOne-VL-2B
- MiniCPM5-2B vs WeVisOne-VL-2B
- MiniMax-M2.5 vs WeVisOne-VL-2B
- MiniMax-M2.7 vs WeVisOne-VL-2B
- MiniMax-M3.1-Flash vs WeVisOne-VL-2B
- Mistral Large 4 vs WeVisOne-VL-2B
- Muse Glimmer 30B vs WeVisOne-VL-2B
- Nanbeige4.2-3B vs WeVisOne-VL-2B
- Nanbeige4.3-33B vs WeVisOne-VL-2B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs WeVisOne-VL-2B
- Nemotron 3.5 Lightning 30B A3B vs WeVisOne-VL-2B
- Nemotron 3 Nano 30B A3B vs WeVisOne-VL-2B
- Nemotron 3 Nano 4B vs WeVisOne-VL-2B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs WeVisOne-VL-2B
- Nemotron 3 Super 120B A12B vs WeVisOne-VL-2B
- Nemotron 3 Ultra 550B A55B vs WeVisOne-VL-2B
- North Mini Code 1.0 vs WeVisOne-VL-2B
- occamy-1.0 vs WeVisOne-VL-2B
- Olmo 3 7B Think vs WeVisOne-VL-2B
- Ornith-1.5-122B vs WeVisOne-VL-2B
- Ornith-1.5-35B-A3B vs WeVisOne-VL-2B
- Ornith-1.5-397B vs WeVisOne-VL-2B
- Ornith-1.5-9B vs WeVisOne-VL-2B
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-2B
- Qwen-AgentWorld-35B-A3B vs WeVisOne-VL-2B
- Qwen3-30B-A3B-Instruct-2507 vs WeVisOne-VL-2B
- Qwen3-4B-Instruct-2507 vs WeVisOne-VL-2B
- Qwen3.5-0.8B vs WeVisOne-VL-2B
- Qwen3.5-122B-A10B vs WeVisOne-VL-2B
- Qwen3.5-2B vs WeVisOne-VL-2B
- Qwen3.5-397B-A17B vs WeVisOne-VL-2B
- Qwen3.5-4B vs WeVisOne-VL-2B
- Qwen3.5-9B vs WeVisOne-VL-2B
- Qwen3.6-27B vs WeVisOne-VL-2B
- Qwen3.6-35B-A3B vs WeVisOne-VL-2B
- Qwen3.8-27B vs WeVisOne-VL-2B
- Qwen3.8-Flash-Next vs WeVisOne-VL-2B
- Qwen3-Coder-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-Coder-Next vs WeVisOne-VL-2B
- Qwen3-Omni-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-2B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-32B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-4B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-8B-Instruct vs WeVisOne-VL-2B
- Qwopus3.8-27B-Flash-V2 vs WeVisOne-VL-2B
- Recursive Flint vs WeVisOne-VL-2B
- Ripple-65B Preview vs WeVisOne-VL-2B
- SenseNova-Loop-9B-Preview vs WeVisOne-VL-2B
- SmolLM3-3B vs WeVisOne-VL-2B
- Spark-X2.6-4B vs WeVisOne-VL-2B
- Step 3.7 Flash vs WeVisOne-VL-2B
- Swift 1.5 Qwen3.8-27B vs WeVisOne-VL-2B
- Swift 1.5 Qwen3.8-Flash-Next vs WeVisOne-VL-2B
- ThinkingCap (Qwen3.8 27B) vs WeVisOne-VL-2B
- WeVisOne-VL-2B vs WeVisOne-VL-4B
- WeVisOne-VL-2B vs ZAYA1-8B
- Baidu Unlimited-OCR-2 vs WeVisOne-VL-2B
Machine-readable
- This page as Markdown
/compare/kimi-k3-vs-wevisone-vl-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kimi-k3.json·/api/v1/tools/wevisone-vl-2b.json - From a terminal
anchor compare kimi-k3 wevisone-vl-2b(the CLI) - Over MCP
compare_tools {"a": "kimi-k3", "b": "wevisone-vl-2b"}at/mcp, no key