Head to head · Open-weight models you run yourself · October 2026 research run
Kimi K3 vs Ling-3.1-flash-1019
Kimi K3 scores 62.4 (B) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 2 of 4 scored categories. Ling-3.1-flash-1019 leads on reach 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 4969 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 45
- Agent interface, 65 against 60
Watch for
1,561 GB of files at its smallest publisher build, far beyond any single machine
Best for Teams with a multi-GPU server that want an MIT-licensed flagship for long agent runs and coding
Ahead on
- Reach, 60 against 50
- Documentation and upkeep, 56 against 41
Watch for
574 GB in FP8 with no smaller build from inclusionAI, so no single machine under 690 GB of GPU memory runs it
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.
Risk Kimi K3 +20
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.
Ling-3.1-flash-1019 45
File safety 15, safetensors only, no .bin, .pt or .pth files (25), less 10 because the card's documented vLLM command passes --trust-remote-code, which runs the repository's configuration_bailing_moe_v3.py, since vLLM 0.33.0 registers no bailing_hybrid config of its own. Provenance 15, files in the inclusionAI organisation that inclusion-ai.org links to, per the Ling-3.0-tiny listing (10). Safety evaluation 0, no safety results for the model on its card or in the training-content summary. Agent guidance 0, the card has nothing on prompt injection, refusals or safeguards, and inclusionAI publishes no guardrail probe for this model as it did for Ling 3.0. Licence risk 15, MIT with no use policy, no field-of-use limits, no threshold and no clause letting inclusionAI change or revoke it. Security programme 0, www.inclusion-ai.org answers 404 for security.txt on 10 November 2026, and the Ling-3.0-tiny listing found no SECURITY.md or disclosure policy in the inclusionAI .github repository. 15 + 15 + 0 + 0 + 15 + 0 = 45.
Documentation and upkeep Ling-3.1-flash-1019 +15
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.
Ling-3.1-flash-1019 56
Model card 11, Intended use (complex reasoning, multi-step tasks and agentic workflows), architecture, parameters (560B total, 25B active) and context (1M claimed) are on the card. Training data 15, the training-content summary the card links names the source categories (Common Crawl and other public datasets, commercially licensed data, the Ant Spider crawler, synthetic data), the size band (over 10 trillion text tokens), data collected up to about July 2026 and the filtering, without listing datasets with sizes. Last change 20, the newest commit, on 4 November 2026, edited the card, six days before this check, and the files went up on 27 October. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (both opened on 27 October 2026) has a reply from an inclusionAI member. Version policy 5, the update went into a repository of its own and Ling-3.1-flash and Ling 3.0 stay in theirs. File health 5, the card states a 1M-token context while config.json gives 262,144 with no rope scaling, and its serve commands name the earlier repository as the model path. 11 + 15 + 20 + 0 + 5 + 5 = 56.
Reach Ling-3.1-flash-1019 +10
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.
Ling-3.1-flash-1019 60
Memory 0, inclusionAI's only build is the FP8 release at 573.78 GB, × 1.2 = 688.5 GB, above 256 GB, and no runtime's library has a build. Runtimes 25, Released model code in Transformers 5.22.2 (bailing_hybrid), vLLM 0.33.0 (BailingMoeV3ForCausalLM, with ling3 tool and reasoning parsers), SGLang 0.5.23 (bailing_moe_v3.py, its bailing_hybrid config and MTP module) and llama.cpp b12242 (bailingmoe3), and Ollama, credited through its pinned llama.cpp as on the Ling-3.0-tiny listing: v0.40.16 sets LLAMA_CPP_VERSION to b12177. Builds 10, the release is FP8, the one quantised precision inclusionAI publishes for it. Terms 15, MIT in the card's metadata, with no use policy or other terms added on the card or in the repository. Download 10, the Hub API's model info gives gated false on 10 November 2026, so the files download with no account and no terms to accept. Hosted 0, the Hub API's provider mapping is empty for this repository on 10 November 2026. 0 + 25 + 10 + 15 + 10 + 0 = 60.
Agent interface Kimi K3 +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.
Ling-3.1-flash-1019 60
Chat template 20, chat_template.jinja in the repository (6,042 characters), which handles tools, the thinking switch and preserved reasoning. Tool-calling format 10, only the template says how tools are declared (JSON in <tools>) and how calls come back (<tool_call>name with <arg_key> and <arg_value> pairs). Trained tool calling 20, the template tells the model it may call one or more functions and loops over every entry in an assistant message's tool_calls, and the card reports gains on agentic benchmarks, AA-Briefcase and AutomationBench-AA among them. Structured output 0, the card doesn't document JSON or JSON Schema output. Reasoning control 0, the card documents turning thinking on or off per request with chat_template_kwargs enable_thinking, and names the ling3 reasoning parser, but doesn't say where the reasoning text comes back. Context 10, 262,144 tokens natively in config.json (max_position_embeddings 262144, rope_scaling null) and per SGLang's cookbook. 20 + 10 + 20 + 0 + 0 + 10 = 60.
Score by category
| Category | Weight this run | Kimi K3 | Ling-3.1-flash-1019 | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 50 | 60 | Ling-3.1-flash-1019 +10 |
| Risk | 20%20 | 65 | 45 | Kimi K3 +20 |
| Agent interface | 10%10 | 65 | 60 | Kimi K3 +5 |
| Documentation and upkeep | 10%10 | 41 | 56 | Ling-3.1-flash-1019 +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.4/100 | C 54.8/100 |
Facts side by side
| Fact | Kimi K3 | Ling-3.1-flash-1019 |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Moonshot AI | inclusionAI (Ant Group) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Kimi K3 License (modified MIT) | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-09-02 | 2026-11-04 |
| Terms last updated | no document linked | no document linked |
| 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.
Ling-3.1-flash-1019
inclusionAI's newest flagship, a 560B hybrid mixture of experts under plain MIT that vLLM, SGLang, Transformers and llama.cpp run in released versions. It ships only as 574 GB of FP8, so it needs a multi-GPU server. The card overstates the context, documents little about tool calls, and has 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
Ling-3.1-flash-1019
- Serve it with SGLang 0.5.23 or later on 8 H200 or 4 GB300 GPUs, per the card, and use this repository's name as the model path, not the earlier one the card's command shows
- With vLLM pass
--trust-remote-code,--tool-call-parser ling3and--reasoning-parser ling3 - Set
chat_template_kwargsenable_thinkingfalse for direct answers. Reasoning comes back inreasoning_contentper SGLang's cookbook - Plan on 262,144 tokens of context. The 1M figure needs the YaRN override in SGLang's cookbook
- Use temperature 1.0, top_p 0.95 and top_k 20, per the card
- Validate JSON output yourself, since structured output isn't documented
Questions
Which is better for AI agents, Kimi K3 or Ling-3.1-flash-1019?
Kimi K3 scores 62.4 (B) on agent readiness against Ling-3.1-flash-1019's 54.8 (C), and leads in 2 of 4 scored categories. Ling-3.1-flash-1019 leads on reach and documentation and upkeep.
Other comparisons with Kimi K3 or Ling-3.1-flash-1019
- Agents-A1-4B vs Kimi K3
- Agents-A1-4B vs Ling-3.1-flash-1019
- Apertus v1.5 8B vs Kimi K3
- Apertus v1.5 8B vs Ling-3.1-flash-1019
- Apodex-1.1-mini vs Kimi K3
- Apodex-1.1-mini vs Ling-3.1-flash-1019
- Arete-27B vs Kimi K3
- Arete-27B vs Ling-3.1-flash-1019
- BigBang-v1 vs Kimi K3
- BigBang-v1 vs Ling-3.1-flash-1019
- Carbon-X vs Kimi K3
- Carbon-X vs Ling-3.1-flash-1019
- Cosmos-Reason2-2B vs Kimi K3
- Cosmos-Reason2-2B vs Ling-3.1-flash-1019
- Darwin-36B-Opus vs Kimi K3
- Darwin-36B-Opus vs Ling-3.1-flash-1019
- DeepSeek-V3.2 vs Kimi K3
- DeepSeek-V3.2 vs Ling-3.1-flash-1019
- DeepSeek V4.1 Flash vs Kimi K3
- DeepSeek V4.1 Flash vs Ling-3.1-flash-1019
- DeepSeek-V4-Flash-0731 vs Kimi K3
- DeepSeek-V4-Flash-0731 vs Ling-3.1-flash-1019
- DiffusionGemma 26B A4B IT vs Kimi K3
- DiffusionGemma 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 12B IT vs Kimi K3
- Gemma 4 12B IT vs Ling-3.1-flash-1019
- Gemma 4 26B A4B IT vs Kimi K3
- Gemma 4 26B A4B IT vs Ling-3.1-flash-1019
- Gemma 4 31B IT vs Kimi K3
- Gemma 4 31B IT vs Ling-3.1-flash-1019
- Gemma 4 E2B IT vs Kimi K3
- Gemma 4 E2B IT vs Ling-3.1-flash-1019
- Gemma 4 E4B IT vs Kimi K3
- Gemma 4 E4B IT vs Ling-3.1-flash-1019
- GLM-4.5-Air vs Kimi K3
- GLM-4.5-Air vs Ling-3.1-flash-1019
- GLM-4.7-Flash vs Kimi K3
- GLM-4.7-Flash vs Ling-3.1-flash-1019
- GLM-5.3-Flash vs Kimi K3
- GLM-5.3-Flash vs Ling-3.1-flash-1019
- GLM-5.3 vs Kimi K3
- GLM-5.3 vs Ling-3.1-flash-1019
- gpt-oss-120b vs Kimi K3
- gpt-oss-120b vs Ling-3.1-flash-1019
- gpt-oss-20b vs Kimi K3
- gpt-oss-20b vs Ling-3.1-flash-1019
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 30B vs Ling-3.1-flash-1019
- Granite 4.2 3B vs Kimi K3
- Granite 4.2 3B vs Ling-3.1-flash-1019
- Granite 4.2 8B vs Kimi K3
- Granite 4.2 8B vs Ling-3.1-flash-1019
- Hy-Memory-30B-A3B vs Kimi K3
- Hy-Memory-30B-A3B vs Ling-3.1-flash-1019
- Hy3 vs Kimi K3
- Hy3 vs Ling-3.1-flash-1019
- Inkling-Small vs Kimi K3
- Inkling-Small vs Ling-3.1-flash-1019
- Inkling vs Kimi K3
- Inkling vs Ling-3.1-flash-1019
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Kimi K3
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs Ling-3.1-flash-1019
- Kimi K3.1 Pro vs Ling-3.1-flash-1019
- 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 MiMo-V2.6 Distill Qwen 9B
- 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.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 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 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 SmolLM3-3B
- Kimi K3 vs Spark-X2.6-4B
- 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
- Kolibri-1 vs Ling-3.1-flash-1019
- Kronos vs Ling-3.1-flash-1019
- Laguna M.1 vs Ling-3.1-flash-1019
- Laguna S 2.1 vs Ling-3.1-flash-1019
- Laguna XS 2.1 vs Ling-3.1-flash-1019
- LBS-27B vs Ling-3.1-flash-1019
- LFM2.5-2.6B vs Ling-3.1-flash-1019
- LFM3-1.7B vs Ling-3.1-flash-1019
- LFM3-Audio-2B vs Ling-3.1-flash-1019
- LFM3-Omni-2B vs Ling-3.1-flash-1019
- LFM3-VL-2B vs Ling-3.1-flash-1019
- Ling-3.0-tiny vs Ling-3.1-flash-1019
- Ling-3.1-flash-1019 vs MiMo-V2.6 Distill Qwen 9B
- Ling-3.1-flash-1019 vs MiniCPM-o 4.5
- Ling-3.1-flash-1019 vs MiniCPM-V 4.7 1B
- Ling-3.1-flash-1019 vs MiniCPM-V 4.7 35B-A3B
- Ling-3.1-flash-1019 vs MiniCPM5-2B
- Ling-3.1-flash-1019 vs MiniMax-M2.5
- Ling-3.1-flash-1019 vs MiniMax-M2.7
- Ling-3.1-flash-1019 vs MiniMax-M3.1-Flash
- Ling-3.1-flash-1019 vs Mistral Large 4
- Ling-3.1-flash-1019 vs Muse Glimmer 30B
- Ling-3.1-flash-1019 vs Nanbeige4.3-33B
- Ling-3.1-flash-1019 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Ling-3.1-flash-1019 vs Nemotron 3.5 Lightning 30B A3B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano 30B A3B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano 4B
- Ling-3.1-flash-1019 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Ling-3.1-flash-1019 vs Nemotron 3 Super 120B A12B
- Ling-3.1-flash-1019 vs Nemotron 3 Ultra 550B A55B
- Ling-3.1-flash-1019 vs occamy-1.0
- Ling-3.1-flash-1019 vs Olmo 3 7B Think
- Ling-3.1-flash-1019 vs Ornith-1.5-122B
- Ling-3.1-flash-1019 vs Ornith-1.5-35B-A3B
- Ling-3.1-flash-1019 vs Ornith-1.5-397B
- Ling-3.1-flash-1019 vs Ornith-1.5-9B
- Ling-3.1-flash-1019 vs Qwen-AgentWorld-35B-A3B
- Ling-3.1-flash-1019 vs Qwen3-30B-A3B-Instruct-2507
- Ling-3.1-flash-1019 vs Qwen3-4B-Instruct-2507
- Ling-3.1-flash-1019 vs Qwen3.5-0.8B
- Ling-3.1-flash-1019 vs Qwen3.5-122B-A10B
- Ling-3.1-flash-1019 vs Qwen3.5-2B
- Ling-3.1-flash-1019 vs Qwen3.5-397B-A17B
- Ling-3.1-flash-1019 vs Qwen3.5-4B
- Ling-3.1-flash-1019 vs Qwen3.5-9B
- Ling-3.1-flash-1019 vs Qwen3.6-27B
- Ling-3.1-flash-1019 vs Qwen3.6-35B-A3B
- Ling-3.1-flash-1019 vs Qwen3.8-27B
- Ling-3.1-flash-1019 vs Qwen3.8-Flash-Next
- Ling-3.1-flash-1019 vs Qwen3-Coder-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-Coder-Next
- Ling-3.1-flash-1019 vs Qwen3-Omni-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-2B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-30B-A3B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-32B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-4B-Instruct
- Ling-3.1-flash-1019 vs Qwen3-VL-8B-Instruct
- Ling-3.1-flash-1019 vs Qwopus3.8-27B-Flash-V2
- Ling-3.1-flash-1019 vs Recursive Flint
- Ling-3.1-flash-1019 vs Ripple-65B Preview
- Ling-3.1-flash-1019 vs SmolLM3-3B
- Ling-3.1-flash-1019 vs Spark-X2.6-4B
- Ling-3.1-flash-1019 vs Swift 1.5 Qwen3.8-27B
- Ling-3.1-flash-1019 vs Swift 1.5 Qwen3.8-Flash-Next
- Ling-3.1-flash-1019 vs ThinkingCap (Qwen3.8 27B)
- Ling-3.1-flash-1019 vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/kimi-k3-vs-ling-3-1-flash-1019.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/kimi-k3.json·/api/v1/tools/ling-3-1-flash-1019.json - From a terminal
anchor compare kimi-k3 ling-3-1-flash-1019(the CLI) - Over MCP
compare_tools {"a": "kimi-k3", "b": "ling-3-1-flash-1019"}at/mcp, no key