Head to head · Open-weight models you run yourself · October 2026 research run
Cosmos-Reason2-2B vs Granite 4.2 30B
Granite 4.2 30B scores 61 (C) on agent readiness against Cosmos-Reason2-2B's 59.5 (C), and leads in 3 of 4 scored categories. Cosmos-Reason2-2B leads on risk. 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
Best for Agents that need a small local model to reason over camera footage and images for robotics, driving or smart spaces
Ahead on
- Risk, 60 against 55
Watch for
Gated behind a click-through licence that needs a Hugging Face account
Best for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 24 GB card
Ahead on
- Reach, 90 against 65
- Agent interface, 85 against 65
- Documentation and upkeep, 87 against 39
Watch for
No safety results published for 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.
Documentation and upkeep Granite 4.2 30B +48
Cosmos-Reason2-2B 39
The card misses languages and a cut-off (14). Training data is named by dataset without sizes or a cut-off (5). The Hub repository last changed on 30 April 2026, 188 days before this check, which alone gives 5. NVIDIA's GitHub repository last changed with a README redirect to Cosmos 3 on 7 June 2026, 150 days back, and this run counts the publisher's documentation commits on this line (10). None of its 3 discussions has an NVIDIA reply, counted by author flags on 4 November (0). The 2B's weights were replaced in place in March with a dated line, and the family is now superseded by Cosmos 3 with a dated note (5). The gated files couldn't be checked against the card, which itself mixes float16 and BF16 and links a newer licence than the gate shows (5). 14 + 5 + 10 + 0 + 5 + 5 = 39.
Granite 4.2 30B 87
Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 30B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 15, the last commit to the repository was on 4 September 2026, 67 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (28 August to 3 November 2026), 3 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 30B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 15 + 20 + 5 + 10 = 87.
Reach Granite 4.2 30B +25
Cosmos-Reason2-2B 65
Memory earns the full 30 because the BF16 file is 4.9 GB, about 5.9 GB with the fifth added, though NVIDIA itself asks for 24 GB of GPU memory. Runtimes get 20 because the model keeps Qwen3-VL's architecture, which Transformers, vLLM, SGLang and llama.cpp run in released versions, while LM Studio's catalogue has only the base. Builds score 0, as NVIDIA publishes no quantised build of the 2B. The NVIDIA Open Model License allows free commercial use under a use policy (10). The gate is an automatic click-through that needs an account (5), and nothing hosts the 2B (0).
Granite 4.2 30B 90
Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 GB, which fits 24 GB but not 16 GB. Its Q4_0 GGUF is 16.58 GB and Ollama's library build granite4.2:30b 18 GB, the same band. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 30b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 25 + 25 + 15 + 15 + 10 + 0 = 90.
Agent interface Granite 4.2 30B +20
Cosmos-Reason2-2B 65
A Jinja template ships as chat_template.json (20). Tools are declared only by the template it inherits from Qwen3-VL, with no NVIDIA documentation or parser (10), and nothing shows the 2B was trained for tool use (0). NVIDIA's prompt files ask for JSON with named keys for boxes, events and trajectories (15). Reasoning is asked for in the prompt and vLLM's qwen3 parser returns it apart (10). The card states 256K input tokens (10).
Granite 4.2 30B 85
Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.
Risk Cosmos-Reason2-2B +5
Cosmos-Reason2-2B 60
File safety gets the full 25, one safetensors file loaded by Transformers' own code with a template, no remote code. Provenance gets 15 for files in NVIDIA's own organisation with hashes. The licence has a use policy and guardrail clause and NVIDIA can revoke or update it, so licence risk keeps 5 of 15. NVIDIA's PSIRT route and bulletins give the security programme 10. Agent guidance gets 5 for general cautions about guardrails and physical risk, and safety evaluation 0, with no safety results.
Granite 4.2 30B 55
File safety 15, safetensors only, no .bin, .pt or .pth files (25). Provenance 15, the files sit in the ibm-granite organisation, which IBM's Granite docs and the GitHub README link to (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions. Licence risk 15, Apache 2.0 has no use policy, field-of-use limit, threshold or change clause, and the card's licence link resolves. Security programme 5, www.ibm.com/.well-known/security.txt names IBM PSIRT, read for the 3B listing on 4 November 2026 (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.
Score by category
| Category | Weight this run | Cosmos-Reason2-2B | Granite 4.2 30B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 65 | 90 | Granite 4.2 30B +25 |
| Risk | 20%20 | 60 | 55 | Cosmos-Reason2-2B +5 |
| Agent interface | 10%10 | 65 | 85 | Granite 4.2 30B +20 |
| Documentation and upkeep | 10%10 | 39 | 87 | Granite 4.2 30B +48 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 59.5/100 | C 61/100 |
Facts side by side
| Fact | Cosmos-Reason2-2B | Granite 4.2 30B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | NVIDIA | IBM |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | NVIDIA Open Model License (custom, commercial use allowed, not an OSI licence); built on Qwen3-VL-2B-Instruct under Apache 2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-03-10 | 2026-09-04 |
| Terms last updated | 2025-10-24 | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 2.5/5 (4) | none |
Verdicts
Cosmos-Reason2-2B
A small local model for reasoning over video and images in robotics, driving and warehouse scenes, returning points, boxes and timed events as JSON. The 4.9 GB file runs in Transformers or vLLM, though NVIDIA asks for 24 GB of GPU memory. Development has moved to Cosmos 3, and the gated licence is revocable.
Granite 4.2 30B
IBM's largest reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 24 GB card, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.
Before you call either
Cosmos-Reason2-2B
- Accept the licence on the Hugging Face card with a signed-in account and set HF_TOKEN before downloading
- Serve it with
vllm serve nvidia/Cosmos-Reason2-2B --max-model-len 16384 --media-io-kwargs '{"video": {"num_frames": -1}}' --reasoning-parser qwen3, keeping max-model-len between 8,192 and 16,384 as NVIDIA advises - For local video or images, make a folder for them (
mkdir -p media) and pass--allowed-local-media-path "$(pwd)/media", so the server can read only that folder, not everything under the directory you start it from - Sample video at 4 fps and allow at least 4,096 output tokens so the reasoning isn't cut off
- For reasoning, add the card's instruction to answer with a think block and then the answer; leave it out for a direct reply
- Use NVIDIA's prompt files (prompts/*.yaml in nvidia-cosmos/cosmos-reason2) when you want JSON boxes, events or trajectories, and validate the JSON yourself
- Check its plans before a robot acts on them, since NVIDIA's own safety card warns of collision and manipulation risks
Granite 4.2 30B
- Start it with
ollama run granite4.2:30b, orllama-server -hf ibm-granite/granite-4.2-30b-GGUF:Q4_K_M --jinja - With vLLM 0.32.0 or later leave out
--reasoning-parser-plugin, since the parser is built in, and use--tool-call-parser qwen3_coder - Thinking is on by default. Pass
enable_thinkingfalse to turn it off orlow_efforttrue for short reasoning - The context is 131,072 tokens. The card's 512K extension isn't documented
- Validate JSON output yourself, since structured output isn't documented
- IBM recommends Granite Guardian beside it to flag risky inputs and outputs
Questions
Which is better for AI agents, Cosmos-Reason2-2B or Granite 4.2 30B?
Granite 4.2 30B scores 61 (C) on agent readiness against Cosmos-Reason2-2B's 59.5 (C), and leads in 3 of 4 scored categories. Cosmos-Reason2-2B leads on risk.
Other comparisons with Cosmos-Reason2-2B or Granite 4.2 30B
- Agents-A1-4B vs Cosmos-Reason2-2B
- Agents-A1-4B vs Granite 4.2 30B
- Apertus v1.5 8B vs Cosmos-Reason2-2B
- Apertus v1.5 8B vs Granite 4.2 30B
- Apodex-1.1-mini vs Cosmos-Reason2-2B
- Apodex-1.1-mini vs Granite 4.2 30B
- Arete-27B vs Cosmos-Reason2-2B
- Arete-27B vs Granite 4.2 30B
- BigBang-v1 vs Cosmos-Reason2-2B
- BigBang-v1 vs Granite 4.2 30B
- Carbon-X vs Cosmos-Reason2-2B
- Carbon-X vs Granite 4.2 30B
- Cosmos-Reason2-2B vs Darwin-36B-Opus
- Cosmos-Reason2-2B vs DeepSeek-V3.2
- Cosmos-Reason2-2B vs DeepSeek V4.1 Flash
- Cosmos-Reason2-2B vs DeepSeek-V4-Flash-0731
- Cosmos-Reason2-2B vs DiffusionGemma 26B A4B IT
- Cosmos-Reason2-2B vs Gemma 4 12B IT
- Cosmos-Reason2-2B vs Gemma 4 26B A4B IT
- Cosmos-Reason2-2B vs Gemma 4 31B IT
- Cosmos-Reason2-2B vs Gemma 4 E2B IT
- Cosmos-Reason2-2B vs Gemma 4 E4B IT
- Cosmos-Reason2-2B vs GLM-4.5-Air
- Cosmos-Reason2-2B vs GLM-4.7-Flash
- Cosmos-Reason2-2B vs GLM-5.3
- Cosmos-Reason2-2B vs GLM-5.3-Flash
- Cosmos-Reason2-2B vs gpt-oss-120b
- Cosmos-Reason2-2B vs gpt-oss-20b
- Cosmos-Reason2-2B vs Granite 4.2 3B
- Cosmos-Reason2-2B vs Granite 4.2 8B
- Cosmos-Reason2-2B vs Hy-Memory-30B-A3B
- Cosmos-Reason2-2B vs Hy3
- Cosmos-Reason2-2B vs Inkling
- Cosmos-Reason2-2B vs Inkling-Small
- Cosmos-Reason2-2B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Cosmos-Reason2-2B vs Kimi K3
- Cosmos-Reason2-2B vs Kimi K3.1 Pro
- Cosmos-Reason2-2B vs Kolibri-1
- Cosmos-Reason2-2B vs Kronos
- Cosmos-Reason2-2B vs Laguna M.1
- Cosmos-Reason2-2B vs Laguna S 2.1
- Cosmos-Reason2-2B vs Laguna XS 2.1
- Cosmos-Reason2-2B vs LBS-27B
- Cosmos-Reason2-2B vs LFM2.5-2.6B
- Cosmos-Reason2-2B vs LFM3-1.7B
- Cosmos-Reason2-2B vs LFM3-Audio-2B
- Cosmos-Reason2-2B vs LFM3-Omni-2B
- Cosmos-Reason2-2B vs LFM3-VL-2B
- Cosmos-Reason2-2B vs Ling-3.0-tiny
- Cosmos-Reason2-2B vs Ling-3.1-flash-1019
- Cosmos-Reason2-2B vs MiMo-V2.6 Distill Qwen 9B
- Cosmos-Reason2-2B vs MiniCPM-o 4.5
- Cosmos-Reason2-2B vs MiniCPM-V 4.7 1B
- Cosmos-Reason2-2B vs MiniCPM-V 4.7 35B-A3B
- Cosmos-Reason2-2B vs MiniCPM5-2B
- Cosmos-Reason2-2B vs MiniMax-M2.5
- Cosmos-Reason2-2B vs MiniMax-M2.7
- Cosmos-Reason2-2B vs MiniMax-M3.1-Flash
- Cosmos-Reason2-2B vs Mistral Large 4
- Cosmos-Reason2-2B vs Muse Glimmer 30B
- Cosmos-Reason2-2B vs Nanbeige4.3-33B
- Cosmos-Reason2-2B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Cosmos-Reason2-2B vs Nemotron 3.5 Lightning 30B A3B
- Cosmos-Reason2-2B vs Nemotron 3 Nano 30B A3B
- Cosmos-Reason2-2B vs Nemotron 3 Nano 4B
- Cosmos-Reason2-2B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Cosmos-Reason2-2B vs Nemotron 3 Super 120B A12B
- Cosmos-Reason2-2B vs Nemotron 3 Ultra 550B A55B
- Cosmos-Reason2-2B vs occamy-1.0
- Cosmos-Reason2-2B vs Olmo 3 7B Think
- Cosmos-Reason2-2B vs Ornith-1.5-122B
- Cosmos-Reason2-2B vs Ornith-1.5-35B-A3B
- Cosmos-Reason2-2B vs Ornith-1.5-397B
- Cosmos-Reason2-2B vs Ornith-1.5-9B
- Cosmos-Reason2-2B vs Qwen-AgentWorld-35B-A3B
- Cosmos-Reason2-2B vs Qwen3-30B-A3B-Instruct-2507
- Cosmos-Reason2-2B vs Qwen3-4B-Instruct-2507
- Cosmos-Reason2-2B vs Qwen3.5-0.8B
- Cosmos-Reason2-2B vs Qwen3.5-122B-A10B
- Cosmos-Reason2-2B vs Qwen3.5-2B
- Cosmos-Reason2-2B vs Qwen3.5-397B-A17B
- Cosmos-Reason2-2B vs Qwen3.5-4B
- Cosmos-Reason2-2B vs Qwen3.5-9B
- Cosmos-Reason2-2B vs Qwen3.6-27B
- Cosmos-Reason2-2B vs Qwen3.6-35B-A3B
- Cosmos-Reason2-2B vs Qwen3.8-27B
- Cosmos-Reason2-2B vs Qwen3.8-Flash-Next
- Cosmos-Reason2-2B vs Qwen3-Coder-30B-A3B-Instruct
- Cosmos-Reason2-2B vs Qwen3-Coder-Next
- Cosmos-Reason2-2B vs Qwen3-Omni-30B-A3B-Instruct
- Cosmos-Reason2-2B vs Qwen3-VL-2B-Instruct
- Cosmos-Reason2-2B vs Qwen3-VL-30B-A3B-Instruct
- Cosmos-Reason2-2B vs Qwen3-VL-32B-Instruct
- Cosmos-Reason2-2B vs Qwen3-VL-4B-Instruct
- Cosmos-Reason2-2B vs Qwen3-VL-8B-Instruct
- Cosmos-Reason2-2B vs Qwopus3.8-27B-Flash-V2
- Cosmos-Reason2-2B vs Recursive Flint
- Cosmos-Reason2-2B vs Ripple-65B Preview
- Cosmos-Reason2-2B vs SmolLM3-3B
- Cosmos-Reason2-2B vs Spark-X2.6-4B
- Cosmos-Reason2-2B vs Swift 1.5 Qwen3.8-27B
- Cosmos-Reason2-2B vs Swift 1.5 Qwen3.8-Flash-Next
- Cosmos-Reason2-2B vs ThinkingCap (Qwen3.8 27B)
- Cosmos-Reason2-2B vs Baidu Unlimited-OCR-2
- Darwin-36B-Opus vs Granite 4.2 30B
- DeepSeek-V3.2 vs Granite 4.2 30B
- DeepSeek V4.1 Flash vs Granite 4.2 30B
- DeepSeek-V4-Flash-0731 vs Granite 4.2 30B
- DiffusionGemma 26B A4B IT vs Granite 4.2 30B
- Gemma 4 12B IT vs Granite 4.2 30B
- Gemma 4 26B A4B IT vs Granite 4.2 30B
- Gemma 4 31B IT vs Granite 4.2 30B
- Gemma 4 E2B IT vs Granite 4.2 30B
- Gemma 4 E4B IT vs Granite 4.2 30B
- GLM-4.5-Air vs Granite 4.2 30B
- GLM-4.7-Flash vs Granite 4.2 30B
- GLM-5.3-Flash vs Granite 4.2 30B
- GLM-5.3 vs Granite 4.2 30B
- gpt-oss-120b vs Granite 4.2 30B
- gpt-oss-20b vs Granite 4.2 30B
- Granite 4.2 30B vs Granite 4.2 3B
- Granite 4.2 30B vs Granite 4.2 8B
- Granite 4.2 30B vs Hy-Memory-30B-A3B
- Granite 4.2 30B vs Hy3
- Granite 4.2 30B vs Inkling
- Granite 4.2 30B vs Inkling-Small
- Granite 4.2 30B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Granite 4.2 30B vs Kimi K3
- Granite 4.2 30B vs Kimi K3.1 Pro
- Granite 4.2 30B vs Kolibri-1
- Granite 4.2 30B vs Kronos
- Granite 4.2 30B vs Laguna M.1
- Granite 4.2 30B vs Laguna S 2.1
- Granite 4.2 30B vs Laguna XS 2.1
- Granite 4.2 30B vs LBS-27B
- Granite 4.2 30B vs LFM2.5-2.6B
- Granite 4.2 30B vs LFM3-1.7B
- Granite 4.2 30B vs LFM3-Audio-2B
- Granite 4.2 30B vs LFM3-Omni-2B
- Granite 4.2 30B vs LFM3-VL-2B
- Granite 4.2 30B vs Ling-3.0-tiny
- Granite 4.2 30B vs Ling-3.1-flash-1019
- Granite 4.2 30B vs MiMo-V2.6 Distill Qwen 9B
- Granite 4.2 30B vs MiniCPM-o 4.5
- Granite 4.2 30B vs MiniCPM-V 4.7 1B
- Granite 4.2 30B vs MiniCPM-V 4.7 35B-A3B
- Granite 4.2 30B vs MiniCPM5-2B
- Granite 4.2 30B vs MiniMax-M2.5
- Granite 4.2 30B vs MiniMax-M2.7
- Granite 4.2 30B vs MiniMax-M3.1-Flash
- Granite 4.2 30B vs Mistral Large 4
- Granite 4.2 30B vs Muse Glimmer 30B
- Granite 4.2 30B vs Nanbeige4.3-33B
- Granite 4.2 30B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Granite 4.2 30B vs Nemotron 3.5 Lightning 30B A3B
- Granite 4.2 30B vs Nemotron 3 Nano 30B A3B
- Granite 4.2 30B vs Nemotron 3 Nano 4B
- Granite 4.2 30B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Granite 4.2 30B vs Nemotron 3 Super 120B A12B
- Granite 4.2 30B vs Nemotron 3 Ultra 550B A55B
- Granite 4.2 30B vs occamy-1.0
- Granite 4.2 30B vs Olmo 3 7B Think
- Granite 4.2 30B vs Ornith-1.5-122B
- Granite 4.2 30B vs Ornith-1.5-35B-A3B
- Granite 4.2 30B vs Ornith-1.5-397B
- Granite 4.2 30B vs Ornith-1.5-9B
- Granite 4.2 30B vs Qwen-AgentWorld-35B-A3B
- Granite 4.2 30B vs Qwen3-30B-A3B-Instruct-2507
- Granite 4.2 30B vs Qwen3-4B-Instruct-2507
- Granite 4.2 30B vs Qwen3.5-0.8B
- Granite 4.2 30B vs Qwen3.5-122B-A10B
- Granite 4.2 30B vs Qwen3.5-2B
- Granite 4.2 30B vs Qwen3.5-397B-A17B
- Granite 4.2 30B vs Qwen3.5-4B
- Granite 4.2 30B vs Qwen3.5-9B
- Granite 4.2 30B vs Qwen3.6-27B
- Granite 4.2 30B vs Qwen3.6-35B-A3B
- Granite 4.2 30B vs Qwen3.8-27B
- Granite 4.2 30B vs Qwen3.8-Flash-Next
- Granite 4.2 30B vs Qwen3-Coder-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-Coder-Next
- Granite 4.2 30B vs Qwen3-Omni-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-VL-2B-Instruct
- Granite 4.2 30B vs Qwen3-VL-30B-A3B-Instruct
- Granite 4.2 30B vs Qwen3-VL-32B-Instruct
- Granite 4.2 30B vs Qwen3-VL-4B-Instruct
- Granite 4.2 30B vs Qwen3-VL-8B-Instruct
- Granite 4.2 30B vs Qwopus3.8-27B-Flash-V2
- Granite 4.2 30B vs Recursive Flint
- Granite 4.2 30B vs Ripple-65B Preview
- Granite 4.2 30B vs SmolLM3-3B
- Granite 4.2 30B vs Spark-X2.6-4B
- Granite 4.2 30B vs Swift 1.5 Qwen3.8-27B
- Granite 4.2 30B vs Swift 1.5 Qwen3.8-Flash-Next
- Granite 4.2 30B vs ThinkingCap (Qwen3.8 27B)
- Granite 4.2 30B vs Baidu Unlimited-OCR-2
Machine-readable
- This page as Markdown
/compare/cosmos-reason2-2b-vs-granite-4-2-30b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cosmos-reason2-2b.json·/api/v1/tools/granite-4-2-30b.json - From a terminal
anchor compare cosmos-reason2-2b granite-4-2-30b(the CLI) - Over MCP
compare_tools {"a": "cosmos-reason2-2b", "b": "granite-4-2-30b"}at/mcp, no key