Access record
Provider-reported route, eligibility, allowance and data terms, with a source and checked date.
What can I access?
Measure the setup a developer actually uses.
How FreeBench checks provider access, runs exact model-and-harness setups on versioned coding tasks, grades collected evidence, and reports limits and failures.
Keep the evidence layers separate
Three records answer three questions.
A source can establish what a provider offers. Only an actual harness run can show what happened on a task.
Harness episode
The model, route, harness version, environment, task and observable tool activity for one run.
What actually ran?
Graded result
A deterministic task outcome linked to frozen evidence and reproduced by replay.
What did the evidence show?
A result earns its way into the atlas
How one setup is qualified.
A refusal, timeout or missing artifact is recorded with its cause. It does not become a model score.
- 01
Check the route
Read the current provider catalog and terms before an attempt. If a route is absent or no longer eligible, do not score it.
- 02
Freeze the setup
Record the exact model and route, harness version, task version, runtime and resource ceilings before execution.
- 03
Run through the harness
The harness makes the model call and performs the work. A direct endpoint request cannot qualify a harness-only free tier.
- 04
Grade the collected work
Protected deterministic checks inspect the artifacts. The model's own description of success is not a grade.
- 05
Preserve and replay
Link the result to its transcript, tool activity, usage and artifacts. Replay the grade from frozen evidence before review.
When you open an evaluation
Read the scope before the outcome.
A grade is useful only alongside the configuration, task and denominator it came from. A changed route, harness version or workload is a different result.
Inspect current evaluation records · Compare source-checked offers · About FreeBench
Claim, number, source, implication
- 468 stored catalog records are published [468]
- OpenRouter catalog records synced through 2026-10-23 UTC, linked per model page. A stored record is a provider declaration captured on that date, not a measurement.
- 20 of 468 records are listed at $0.00 input and $0.00 output per 1M tokens [20/468]
- Zero listed token prices in OpenRouter records synced through 2026-10-23 UTC. A $0 listed price is not a quota, rate-limit, access or current-availability guarantee.
- 400 of 468 records declare tool support [400/468]
- Provider-declared tool support in records synced through 2026-10-23 UTC. Declared support is not tested endpoint reliability or agent-harness compatibility.
- General model rankings are not published [0]
- The current release publishes reviewed evidence for exact model × harness setups. A single setup does not establish a broad model ranking.
- 1 record have a free offer recorded as retired [1/468]
- Retirement recorded in the stored catalog record. Retired offers are excluded from the free-listed count above.