Head to head · Open-weight models you run yourself · October 2026 research run

Arete-27B vs Kimi K3

Kimi K3 scores 62.4 (B) on agent readiness against Arete-27B's 55.1 (C), and leads in 2 of 4 scored categories. Arete-27B leads on 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

Arete-27B C

Best for Agents that want Qwen3.8-27B's coding and tool use without its handling of politically sensitive topics, on a 24 GB card or a 128 GB machine

Ahead on

  • Documentation and upkeep, 63 against 41

Watch for

No quantised build from Nous Research, so the GGUF route depends on a third party

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
  • Agent interface, 65 against 60

Watch for

1,561 GB of files at its smallest publisher build, far beyond any single machine

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 Arete-27B +22

Arete-27B 63

Model card 8, no limitations, context length, languages or cut-off. Training data 20, the training pairs and the evaluation set are published with their counts. Last change 20, a commit on 6 November 2026. Responsiveness 0, none of 13 discussions has a reply from Nous Research. Version policy 5, a first release. File health 10, the files agree. 8 + 20 + 20 + 0 + 5 + 10 = 63.

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.

Risk Kimi K3 +10

Arete-27B 55

File safety 25, safetensors only and no remote code. Provenance 15, Nous Research's own organisation, linked from its blog, with a hash on every file. Safety evaluation 0 and agent guidance 0, nothing published on either. Licence risk 15, plain Apache 2.0. Security programme 0, no way to report a flaw found. 25 + 15 + 0 + 0 + 15 + 0 = 55.

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.

Agent interface Kimi K3 +5

Arete-27B 60

Chat template 20, a Jinja file in the repository. Tool-calling format 10, only the template says it. Trained tool calling 20, several calls a turn and agentic work as an intended use. Structured output 0 and reasoning control 0, neither is documented on the card. Context 10, 262,144 tokens native. 20 + 10 + 20 + 0 + 0 + 10 = 60.

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.

Score by category

CategoryWeight this runArete-27BKimi K3Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255050even
Risk20%205565Kimi K3 +10
Agent interface10%106065Kimi K3 +5
Documentation and upkeep10%106341Arete-27B +22
Negative events≤1500
TotalC 55.1/100B 62.4/100

Facts side by side

FactArete-27BKimi K3
KindOpen-weight modelOpen-weight model
VendorNous ResearchMoonshot AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Kimi K3 License (modified MIT)
Read-only variant documentednono
llms.txtnono
Last release2026-11-062026-09-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone2.3/5 (4)

Verdicts

Arete-27B

Qwen3.8-27B with its answers on politically sensitive topics retrained, four days old when read. The training data is published, which is rare. Nous Research ships BF16 only, so a small machine runs it from bartowski's GGUF, and the card documents none of the tool or thinking controls it inherits.

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.

Before you call either

Arete-27B

  1. Start it with llama-server -hf bartowski/NousResearch_Arete-27B-GGUF:Q4_K_M --jinja, a third party's conversion, or serve the BF16 files with vLLM
  2. Use the base's parsers in vLLM, --reasoning-parser qwen3 --tool-call-parser qwen3_coder, and check tool calls first, since the template differs slightly from Qwen3.8-27B's
  3. Thinking switches with enable_thinking in the template. The card's own evaluation ran with it off
  4. Expect answers on politically sensitive topics to differ from Qwen3.8-27B's. That is what the fine-tune is for
  5. Validate JSON output yourself, since structured output isn't documented

Kimi K3

  1. 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
  2. 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
  3. Pass the whole assistant message back every turn, reasoning_content and tool_calls included, or output becomes unstable
  4. Thinking is always on; set reasoning_effort to low or high when max is too slow
  5. Sampling per the card is temperature 1.0, with top-p 0.95 for single-step tasks and 1.0 for agentic ones
  6. 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
  7. Without the hardware, call it through Moonshot's API or an inference provider listed on its Hugging Face page

Questions

Which is better for AI agents, Arete-27B or Kimi K3?

Kimi K3 scores 62.4 (B) on agent readiness against Arete-27B's 55.1 (C), and leads in 2 of 4 scored categories. Arete-27B leads on documentation and upkeep.

Other comparisons with Arete-27B or Kimi K3

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.