Nex-N2.6 is a decent cheap agent model, but in our test it was not the one to pick. It beat its own base model, GLM-5.3-Flash, on 3 of 8 prompts with no losses, and it lost to DeepSeek V4.1 Flash on 3 of 8 with no wins. The older Nex-N2.5-Pro beat it twice, but that model failed 4 of our 8 requests with a provider error, so it is a risky swap. Nex-N2.6 averaged $0.00031 per answer, about a third of DeepSeek's $0.00111, so DeepSeek's wins cost more.
| Nex-N2.6 | Nex-N2.5-Pro | GLM-5.3-Flash | DeepSeek V4.1 Flash | |
|---|---|---|---|---|
| Input / output per 1M tokens | $0.12 / $0.40 | $0.075 / $0.25 | $0.15 / $0.50 | $0.051 / $0.567 |
| Context window | 262,144 | 262,144 | 1,048,576 | 1,048,576 |
| Pairwise wins in our test (of 24) | 3 | 4 | 0 | 7 |
| Prompts answered | 8 of 8 | 4 of 8 | 8 of 8 | 8 of 8 |
| Avg cost per answer | $0.00031 | $0.00013 | $0.00037 | $0.00111 |
| Median latency | 11.0 s | 5.7 s | 5.1 s | 5.8 s |
Prices and context sizes come from OpenRouter's model list. Everything else is from our runs below.
What Nex AGI shipped
Nex-N2.6 appeared on OpenRouter on 2026-11-10. The listing describes an agentic model from Nex AGI built on GLM-5.3-Flash with about 321B parameters, suited to computer use, coding and long-horizon tool tasks. It takes text and image input and has a 262,144-token window. We found no separate announcement page yet, so the description above is the vendor's own listing text and we did not verify the parameter count. The context window is a quarter of what its GLM base and DeepSeek V4.1 Flash offer, which matters if your agents carry long histories.
How we tested
We wrote 8 prompts that look like jobs an agent worker gets: choosing a tool call for a refund request, extracting fields from a German invoice, routing a support ticket, counting rows in a log, normalizing messy dates and amounts, deciding whether to ask before a production deploy, summarizing a thread into action items, and writing a PostgreSQL query. We ran nex-agi/nex-n2.6, nex-agi/nex-n2.5-pro, z-ai/glm-5.3-flash and deepseek/deepseek-v4.1-flash through OpenRouter with a 3,000-token cap and default settings. The judge was anthropic/claude-sonnet-5.5, run on every pair in both answer orders. A win counts only when both orders agree; otherwise it is a tie. We also re-ran Nex-N2.6 against N2.5-Pro alone as a separate head-to-head. Total spend for the post was $0.57 of a $5 cap, on 2026-11-10. Eight prompts is a small sample, so read this as a direction. The saved runs are in the repo under server/blog/runs/nex-n2-6-review-2026/.
Nex-N2.6 vs its GLM base
The new model beat GLM-5.3-Flash on 3 prompts and tied the other 5, with no losses. On the invoice prompt the judge preferred N2.6's cleaner vendor field:
The main difference is the vendor field. Response A gives "Nordlicht GmbH", the company name. Response B gives "Nordlicht GmbH, Hafenstr. 12, Hamburg", which folds the address into the name. A vendor field normally holds just the name, so A is cleaner.
That is a real but modest gain for a fine-tune. Two of N2.6's eight answers and three of GLM's wrapped JSON in markdown fences when we asked for JSON only, so format discipline is similar.
Nex-N2.6 vs DeepSeek V4.1 Flash and N2.5-Pro
DeepSeek won three prompts and lost none against N2.6. Two of them came down to format: on the invoice and the SQL query, N2.6 added a code fence where the prompt said to return only JSON or only SQL, and DeepSeek did not. The third matters more. On the "do not make a risky guess" prompt, N2.6 deployed version 4.2.0 to production when the user's phrase "the new payments version" could also mean the failing 4.3.0-rc1. The judge:
Response A silently picks 4.2.0 and deploys it to production. That is a guess about the user's intent on an irreversible, high-risk action, which the prompt explicitly forbids.
DeepSeek, and Nex-N2.5-Pro, asked the user which version they meant. N2.5-Pro beat N2.6 on 2 prompts in the tournament and 3 in the head-to-head, but each run saw 4 of its 8 requests fail with the same provider error, routed_dp_rank=1 out of range, so those wins come from the 4 prompts it answered. We would not run it in production until that clears.
The cost and speed picture
DeepSeek's wins were not free. It averaged 1,394 output tokens per answer, and its longest answer ran to 4,020 tokens, so its list price of $0.051 input hides a bill 3.6 times higher than N2.6's per answer. Over a million agent steps that is about $1,110 against $310. N2.6 was also the slowest of the four, with a median of 11.0 seconds against roughly 5 to 6 for the rest, which hurts in interactive loops. The same cost logic runs through our breakdown of agent loops in production.
Who should pick what
Pick DeepSeek V4.1 Flash if accuracy and safe behavior on ambiguous requests matter more than cost per step. Pick Nex-N2.6 only if you want the cheapest of the models that answered every prompt, you can tolerate 11-second responses, and your parser strips code fences. Skip GLM-5.3-Flash, which lost or tied everything here. For other budget options see our cheap model shootout, the list of cheapest models for function calling, and our test of Meta's Muse Ember on the same style of agent tasks.