SQL · 6 checks · max 500 tokens · benched 2026-09-16

Kimi K3 vs Kimi K2.7 Code vs Kimi K2.6 vs Kimi K2.5 on top five customers by 2025 spend

Moonshotai models side by side on "Top five customers by 2025 spend": Kimi K2.5 scores 10/10; Kimi K3 is the cheapest answer scoring 8+ at $1.05 per 1,000 runs. Outputs, checks, judge reasons, latency and cost.

The prompt every model received

System

You are a database engineer. Reply with a single SQL statement and nothing else.

User

Tables: customers(id, name) and orders(id, customer_id, amount, ordered_at). Write one standard SQL query that returns each customer's name and their total order amount for calendar year 2025, highest total first, limited to the top 5. Use a JOIN, GROUP BY and ORDER BY.

Rubric for the judge: Correct join and aggregate, filters ordered_at to 2025, sorts descending, limits to 5, portable SQL.

Side by side

Every cell is one OpenRouter call at temperature 0 with the prompt's token cap and reasoning effort "low" where the model supports it. Cost is usage × the catalogue rate in models.json. Quality is one judge call to anthropic/claude-haiku-4.5 against the prompt's rubric, cached per prompt version.

Kimi K3

moonshotai/kimi-k3

9/10

cheapest scoring 8+

Latency: 1.4s
Cost: $0.00105
Per 1,000: $1.05

175 in · 87 out (17 reasoning) · 30 words · checks 6/6

regex
regex
regex
regex
regex
contains

SELECT c.name, SUM(o.amount) AS total_amount
FROM customers c
JOIN orders o ON o.customer_id = c.id
WHERE EXTRACT(YEAR FROM o.ordered_at) = 2025
GROUP BY c.name
ORDER BY total_amount DESC
LIMIT 5;

Judge: Query correctly uses JOIN, GROUP BY, ORDER BY, and LIMIT 5 with proper 2025 filtering; minor deduction because GROUP BY should include c.id to be fully standard-compliant (though c.name alone often works in practice).

Kimi K2.7 Code

moonshotai/kimi-k2.7-code

1/10

Latency: 1.0s
Cost: $0.00181
Per 1,000: $1.81

89 in · 500 out (482 reasoning) · 6 words · checks 1/6

regex
regex
regex
regex
regex
contains

SELECT c.name, COALESCE(SUM(o.amount), 0) AS total_amount

Judge: Output is incomplete - missing FROM clause, JOIN statement, WHERE filter for 2025, GROUP BY, ORDER BY, and LIMIT clauses required by the task.

Kimi K2.6

moonshotai/kimi-k2.6

10/10

Latency: 1.8s
Cost: $0.00846
Per 1,000: $8.46

90 in · 2093 out (2018 reasoning) · 33 words · checks 6/6

regex
regex
regex
regex
regex
contains

SELECT c.name, SUM(o.amount) AS total_amount
FROM customers c
JOIN orders o ON c.id = o.customer_id
WHERE o.ordered_at >= '2025-01-01' AND o.ordered_at < '2026-01-01'
GROUP BY c.id, c.name
ORDER BY total_amount DESC
LIMIT 5;

Judge: Query correctly joins customers and orders, filters 2025 using date range, groups by customer with proper aggregation, orders descending by total, limits to 5, and uses portable standard SQL syntax.

Kimi K2.5

moonshotai/kimi-k2.5

10/10

top judge score

Latency: 1.5s
Cost: $0.00355
Per 1,000: $3.55

90 in · 1561 out (1483 reasoning) · 35 words · checks 6/6

regex
regex
regex
regex
regex
contains

```sql
SELECT c.name, SUM(o.amount) AS total_amount
FROM customers c
JOIN orders o ON c.id = o.customer_id
WHERE o.ordered_at >= '2025-01-01' AND o.ordered_at < '2026-01-01'
GROUP BY c.id, c.name
ORDER BY total_amount DESC
LIMIT 5;
```

Frequently asked

What does this prompt test?

SQL: Correct join and aggregate, filters ordered_at to 2025, sorts descending, limits to 5, portable SQL. The deterministic checks are regex, regex, regex, regex, regex, contains.

Which model should I pick for this task?

If the judge's bar of 8/10 is good enough for you, Kimi K3 at $1.05 per 1,000 runs. If you need the top score, Kimi K2.5 at $3.55 per 1,000 runs.

Same prompt, other families

Run it yourself

Re-run this prompt on Moonshotai with your own OpenRouter key, or tweak the wording and see what changes.