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

Kimi K3 vs Kimi K2.7 Code vs Kimi K2.6 vs Kimi K2.5 on products over 100 units with having

Moonshotai models side by side on "Products over 100 units with HAVING": Kimi K2.5 scores 10/10; Kimi K2.5 is the cheapest answer scoring 8+ at $0.73 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: products(id, name) and order_items(product_id, quantity). Write one standard SQL query that lists product names whose total quantity sold across all order_items is greater than 100. Filter the aggregate with a HAVING clause.

Rubric for the judge: Join, SUM(quantity), GROUP BY product, HAVING > 100; returns names only; no WHERE on the aggregate.

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

10/10

Latency: 826ms
Cost: $0.00073
Per 1,000: $0.73

160 in · 60 out (3 reasoning) · 22 words · checks 4/4

regex
regex
regex
regex

```sql
SELECT p.name
FROM products p
JOIN order_items oi ON oi.product_id = p.id
GROUP BY p.id, p.name
HAVING SUM(oi.quantity) > 100;
```

Judge: Query correctly joins products and order_items, groups by product, uses HAVING with SUM(quantity) > 100, returns only names, and contains no WHERE clause on the aggregate.

Kimi K2.7 Code

moonshotai/kimi-k2.7-code

10/10

Latency: 444ms
Cost: $0.00076
Per 1,000: $0.76

75 in · 202 out (155 reasoning) · 22 words · checks 4/4

regex
regex
regex
regex

```sql
SELECT p.name
FROM products p
JOIN order_items oi ON p.id = oi.product_id
GROUP BY p.id, p.name
HAVING SUM(oi.quantity) > 100;
```

Judge: Query correctly joins products and order_items, groups by product, uses HAVING with SUM(quantity) > 100, returns only names, and contains no WHERE clause on the aggregate.

Kimi K2.6

moonshotai/kimi-k2.6

10/10

Latency: 873ms
Cost: $0.00197
Per 1,000: $1.97

75 in · 474 out (433 reasoning) · 20 words · checks 4/4

regex
regex
regex
regex

SELECT p.name
FROM products p
JOIN order_items oi ON p.id = oi.product_id
GROUP BY p.id, p.name
HAVING SUM(oi.quantity) > 100;

Judge: Query correctly joins tables, groups by product, uses HAVING with SUM(quantity) > 100 filter, returns names only, and contains no WHERE clause on the aggregate.

Kimi K2.5

moonshotai/kimi-k2.5

10/10

top judge scorecheapest scoring 8+

Latency: 1.0s
Cost: $0.00073
Per 1,000: $0.73

75 in · 308 out (271 reasoning) · 20 words · checks 4/4

regex
regex
regex
regex

SELECT p.name FROM products p JOIN order_items oi ON p.id = oi.product_id GROUP BY p.id, p.name HAVING SUM(oi.quantity) > 100;

Judge: Query correctly joins products and order_items, groups by product, uses HAVING with SUM(quantity) > 100, returns only names, and contains no WHERE clause filtering the aggregate.

Frequently asked

What does this prompt test?

SQL: Join, SUM(quantity), GROUP BY product, HAVING > 100; returns names only; no WHERE on the aggregate. The deterministic checks are regex, regex, regex, regex.

Which model should I pick for this task?

If the judge's bar of 8/10 is good enough for you, Kimi K2.5 at $0.73 per 1,000 runs. If you need the top score, Kimi K2.5 at $0.73 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.

Side by side

Kimi K3

Kimi K2.7 Code

Kimi K2.6

Kimi K2.5

Frequently asked

Same prompt, other families

Stop overpaying for AI tools