Claude Haiku 5.5 vs Flint
Task by task
A score turns orange only when that model wins clearly more of the task's test cases. Under each score, the average time per test case on the machine it ran on. Flint spends 3.2× as many thinking tokens per test case.
TaskAClaude Haiku 5.5BFlint
Overall
7025.5s
211m 17s
Agents
6139.5s
1447.7s
Structured Extraction
9013.5s
291m 17s
Coding
8630.6s
141m 19s
Grounded Answers
7613.9s
2957.7s
Instruction Following
9431.5s
352m 28s
Business Logic
6726.0s
101m 20s
Security & permissions
6723.4s
3552.6s
Diagnosis & investigation
1725.5s
057.0s
What you'd run
The build behind each score. Orange marks the faster, smaller, cheaper or longer-context side.
SpecAClaude Haiku 5.5BFlint
Speed
225 tok/s (better)
149 tok/s
Machine
Hosted
Hosted
Memory at 32K
—
—
Context
1M (better)
256K
Cost per run
$0.42
Not measured
Cost per case
$0.0028
Not measured
Time per case
25.5s (better)
1m 17s
Quantization
—
BF16
Harness
openrouter
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