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

Carbon-X vs North Mini Code 1.0

Carbon-X and North Mini Code 1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). North Mini Code 1.0 leads on agent interface. 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

Carbon-X C

Best for Agents that need a second opinion on DNA variants and regulatory regions on a 16 to 24 GB machine, without sending sequences to a hosted model.

Ahead on

  • Reach, 90 against 85
  • Risk, 65 against 60
  • Documentation and upkeep, 72 against 36

Watch for

Not clinically validated and no wet-lab validation reported

North Mini Code 1.0 C

Best for Developers who want a coding agent on their own GPU with a permissive licence

Ahead on

  • Agent interface, 85 against 35

Watch for

No limitations, safety results, languages or data description on the card

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.

Agent interface North Mini Code 1.0 +50

Carbon-X 35

Chat template 20, a Jinja file in the repository. Tool-calling format 10, only the inherited template shows the format and no parser is named. Trained tool calling 0, nothing says it was trained to call tools. Structured output 0, not documented. Reasoning control 0, thinking can be switched off but was never trained, and the card asks you to keep it off. Context 5, 40,960 tokens from the base, though Hugging Face trained at 8,192 and under 16K. Most of what the card documents for agents is Carbon-X as a tool another model calls, which this checklist doesn't read.

North Mini Code 1.0 85

Chat template 20, chat_template.jinja in the repository (12,397 characters). Tool-calling format 25, the card documents how tools are declared (JSON schema through the chat template), how the call and its thinking go back into the history and how results are appended, and names the cohere_command4 tool-call parser for vLLM, which released vLLM has. Trained tool calling 20, the card says the model was specifically trained with tool-use capabilities for agentic coding, with reinforcement learning on verifiable tasks, and the template renders every call in a turn with thinking between them. Structured output 0, JSON schema is for describing tools. Reasoning control 10, the template has a reasoning_effort setting, and the card names the cohere_command4 reasoning parser, which returns thinking apart from the answer. Context 10, 256K tokens per the card, with 64K of output, and 500,000 positions in config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Documentation and upkeep Carbon-X +36

Carbon-X 72

Model card 17, everything but a knowledge cut-off. Training data 15, the mid-training sources and shares are listed, the instruction and fine-tuning data aren't named, and there's no cut-off. Last change 20, 28 October 2026, when config.json, generation_config.json, tokenizer_config.json and tokenizer.py were fixed. Responsiveness 10, organisation members replied to 2 of the 4 questions so far. Version policy 5, a first release whose history was squashed without a note. File health 5, the card now sends llama.cpp users to the publisher's GGUF repository, but the tokenizer config's 131,072 still contradicts the card's 40,960. 17 + 15 + 20 + 10 + 5 + 5 = 72.

North Mini Code 1.0 36

Model card 11, Intended use, the architecture, the parameters and the context are on the card. Training data 0, the card gives the training method and nothing about the data. Last change 10, the main repository last changed on 15 June 2026 (outdated chat templates removed), 148 days before this check, and the draft model's repository on 29 July, 104 days. Responsiveness 0, none of the 11 most recent discussions that aren't pull requests (7 June to 6 November 2026) has a reply from a CohereLabs member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, with each build in its own repository. File health 10, Config, template and card agree on the architecture, and the June commit that removed broken templates says so. 11 + 0 + 10 + 0 + 5 + 10 = 36.

Reach Carbon-X +5

Carbon-X 90

Memory 30, the publisher's Q4_K_M GGUF is 9.6 GB, or 11.6 GB with a fifth added. Runtimes 20, released llama.cpp (from b11742, which added the DNA tokenizer), vLLM, SGLang and Transformers all run it, with no Ollama or LM Studio entry. Builds 15, Hugging Face publishes GGUFs at four precisions. Terms 15, Apache 2.0 on the model and on its Qwen3-14B base. Download 10, nothing is gated. Hosted 0, no inference provider or Hugging Face API serves it.

North Mini Code 1.0 85

Memory 25, the smallest build from Cohere is the w4a16 repository, 19.38 GB, and 19.38 GB × 1.2 = 23.3 GB, within 24 GB. Unsloth's GGUF isn't read for this line. Runtimes 20, Released vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 have the cohere2_moe model, and llama.cpp b12242 has the cohere2moe architecture. Builds 15, Quantised builds from Cohere at two precisions, FP8 and 4-bit weights (w4a16), each in its own repository. Terms 15, Apache 2.0 in the metadata and on the card, an OSI licence with nothing added. Download 10, the Hub API reports gated false for the model and its builds 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. 25 + 20 + 15 + 15 + 10 + 0 = 85.

Risk Carbon-X +5

Carbon-X 65

File safety 15, safetensors and GGUF only, but the documented loading path runs the repository's tokenizer.py through trust_remote_code. Provenance 15, the files are in HuggingFaceBio, which Hugging Face's GitHub repository links, with a checksum on every file. Safety evaluation 10, Hugging Face reports its own dual-use check on sequence editing in the launch post, without numbers or a harness. Agent guidance 5, general cautions only. Licence risk 15, plain Apache 2.0. Security programme 5, Hugging Face's security.txt is a reporting route, and public advisories couldn't be checked.

North Mini Code 1.0 60

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in Cohere's verified CohereLabs organisation, which cohere.com links to per our other Cohere listings (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or safety section, and nothing on prompt injection, instruction priority or what the model refuses. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 5, Cohere's trust centre holds a responsible disclosure policy with a bug bounty, as recorded on our Cohere listings (5). 25 + 15 + 0 + 0 + 15 + 5 = 60.

Score by category

CategoryWeight this runCarbon-XNorth Mini Code 1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259085Carbon-X +5
Risk20%206560Carbon-X +5
Agent interface10%103585North Mini Code 1.0 +50
Documentation and upkeep10%107236Carbon-X +36
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactCarbon-XNorth Mini Code 1.0
KindOpen-weight modelOpen-weight model
VendorHugging Face (HuggingFaceBio)Cohere
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-282026-07-29
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Carbon-X

A DNA specialist cousin that another agent calls for variant-effect and sequence questions, with DNA kept on the machine. Hugging Face's Q4_K_M GGUF needs about 12 GB and Q8_0 about 19 GB, on llama.cpp b11742 or later. It isn't clinically validated, isn't trained for tool calls or reasoning, and its Python tokenizer runs repository code.

North Mini Code 1.0

A coding agent model that fits one 24 GB GPU at 4 bits, trained for tool use, with a 256K context, Apache 2.0 and four released runtimes. It's a research release and reads like one: nothing on limitations, safety or data, the card's run instructions are out of date, and Cohere hasn't answered a question on the repository.

Before you call either

Carbon-X

  1. Quickest start is llama-server -hf HuggingFaceBio/Carbon-X-GGUF:Q8_0 -ngl 99 -c 40960 --jinja --chat-template-kwargs '{"enable_thinking": false}' --temp 0.6 --top-p 0.95 --top-k 20 --min-p 0, on llama.cpp b11742 or later
  2. With vLLM or Transformers pass trust_remote_code, and expect the tokenizer to fetch Qwen/Qwen3-4B-Base at a pinned revision on first load
  3. Keep enable_thinking false and the card's sampling (temperature 0.6, top_p 0.95, top_k 20), the settings every reported result used
  4. Keep DNA in files and pass sequences by name, compute positions and base changes in code and send them as context, the card says the model miscounts long sequences
  5. Only A, C, G and T form 6-mers, so filter N and other IUPAC codes first or they become a single oov token
  6. Strip the dna tags from answers if you need bare sequence, llama.cpp keeps them in the text
  7. Cap max_tokens for next-base questions, long DNA generation is slow and degrades

North Mini Code 1.0

  1. Serve it with vLLM 0.33.0 or later and --tool-call-parser cohere_command4 --reasoning-parser cohere_command4 --enable-auto-tool-choice, with cohere_melody installed
  2. Pass the model's thinking back with its tool calls on every turn. The card says results drop without it
  3. Describe tools in JSON schema and append tool results as a dictionary with the tool role
  4. Use temperature 1.0 and top_p 0.95
  5. For llama.cpp the GGUF files are Unsloth's or bartowski's conversions, not Cohere's
  6. It's text only. Don't send images

Questions

Which is better for AI agents, Carbon-X or North Mini Code 1.0?

Carbon-X and North Mini Code 1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). North Mini Code 1.0 leads on agent interface.

Other comparisons with Carbon-X or North Mini Code 1.0

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.