Submit something for verification

benchr publishes nothing it has not checked. Send the claim and where you saw it work; the review is what turns it into a record.

Submissions are reviewed against vendor documentation before anything is published. If a claim cannot be sourced, it is not published — the review is the product.

What gets published

It is one concrete thing, not a category or a product pitch.
There is an official page, changelog entry or repository that shows the mechanism exists.
You can say what did not work. A submission with no limits reads as marketing.
It is reproducible by someone else with the same tools.

What does not

Screenshots of a chat with no source behind them.
Anything whose evidence is a social post or a video with no documentation.
Product announcements. benchr already tracks releases in the change record.

Build the submission

What can it do?

One sentence. The concrete thing, not the category.

Where does it work?

Model, tool, app or CLI — and the version if you know it.

How do you do it?

The steps you actually followed.

Where can this be checked?

A vendor documentation page, a changelog entry, or a public repository.

What did not work?

The limits you hit. This field is the one that gets a submission accepted.

Nothing is submitted from this page automatically. The button below composes a message in your own mail client so you can see exactly what is sent, and delete anything you would rather not include.