Clover 35B A3B Preview vs Flint
Task by task
A score turns orange only when that model wins clearly more of the task's test cases. The time under each score is the average per test case, on the machine it ran on. Flint spends 1.2× as many thinking tokens per test case.
TaskAClover 35B A3B PreviewBFlint
Overall
3035.1s
211m 17s
Agents
2036.8s
1447.7s
Structured Extraction
4327.5s
291m 17s
Coding
101m 5s
141m 19s
Grounded Answers
4821.0s
2957.7s
Instruction Following
5332.8s
352m 28s
Business Logic
1936.1s
101m 20s
Security & permissions
4725.6s
3552.6s
Diagnosis & investigation
037.0s
057.0s
What you'd run
The build behind each score. Orange marks the faster, smaller, cheaper or longer-context side.
SpecAClover 35B A3B PreviewBFlint
Speed
252 tok/s (better)
149 tok/s
Machine
Hosted
Hosted
Memory at 32K
—
—
Context
—
256K
Cost per run
Not measured
Not measured
Cost per case
Not measured
Not measured
Time per case
35.1s (better)
1m 17s
Quantization
—
BF16
Harness
custom
openrouter
The race
Each model's running score as the test cases go by. The dashed line is a perfect run.
Every test case
Each square is one test case, colored by the model that scored higher.
Agents
Structured Extraction
Coding
Grounded Answers
Instruction Following
Business Logic
Security & permissions
Diagnosis & investigation