Kimi K2.6 vs Minimax M3: 5x the cost for worse results? I ran the tests.

I spent the last 48 hours comparing Kimi K2.6 and Minimax M3 in actual agent workflows.

Not benchmarks.

Real terminal coding, API calls, tool use, and multi-step agent loops.

The result surprised me. M3 solved more tasks, delivered nearly identical quality, and cost dramatically less.

What I tested

• ⁠of the hardest Terminal-Bench tasks
• ⁠Gmail, Slack, GitHub, Drive, Calendar, Notion, and Reddit workflows
• ⁠Same prompts
• ⁠Same tools
• ⁠Same sandbox

Only the model changed.

Terminal coding

Model |Tasks Solved |Cost
| |
M3 |5/10 |$2.80
K2.6 |4/10 |$6.61 K2.6 cost roughly 2.4x more while solving fewer tasks. One example stood out.

A difficult path-tracing-reverse task required 134 terminal round trips. M3 kept grinding and eventually finished it. K2.6 timed out.

Real-world agent tasks

I ran 25 practical workflows:

• ⁠Email summarization
• ⁠Drive organization
• ⁠GitHub analysis
• ⁠Startup research
• ⁠Outreach drafting
• ⁠Cross-app automation

Scoring was simple:

• ⁠= successful completion
• ⁠= failure
• ⁠Average score across all tasks

Results:

Model |Score |Cost
| |
M3 |0.75 |$0.81
K2.6 |0.72 |$4.08 The quality difference was tiny. The cost difference wasn't.

M3 ended up roughly 5x cheaper for almost identical results.

Why this matters

Most model discussions focus on capability. Production workloads care about something else:

• ⁠Cost per completed task
• ⁠Tool-call efficiency
• ⁠Retry rates
• ⁠Context limits

Current pricing:

Minimax M3

• ⁠context window

Kimi K2.6

• ⁠context window

Once agents start making dozens of tool calls, output costs become a much bigger deal than most benchmark charts suggest.

My takeaway

The biggest surprise wasn't that M3 won a few tests. It was how often I forgot I wasn't using a premium model. I'd look at the outputs, assume they were roughly tied, then check the bill and realize K2.6 had cost several times more.

For coding agents, terminal workflows, and cost-sensitive production systems, I'd deploy M3 first.

For research-heavy workflows, K2.6 is still a strong model.

But based on these runs, the value-per-dollar gap wasn't close.

Anyone else running both? What are you seeing in terms of cost per completed task?