Start here
The free tool below runs entirely in this browser — no account, nothing stored or transmitted. Redact anything you would not want kept before you type it.
Open the companion tool →Why the card is the honest part of the marketing
A model card is usually written for technical readers, which makes it less polished than a product page and more informative. Intended use, evaluation results, and limitations sections are where companies state what the system is not good at.
The gaps matter too: a card that reports evaluation on one language, one demographic, or one task is telling you where it has been checked. Absence of evaluation is not proof of failure — it is simply unknown, and worth treating that way.
The protocol
- Find the intended use and out-of-scope sections first. A system built for summarization is being used outside its scope when it advises on medication.
- Look at what was evaluated: which tasks, which languages, which data, and who ran the tests — the developer, or an outside party.
- Read the limitations and known risks section. This is usually the most candid part of the document, and it is written by the people who know the system best.
- Note the date and version. A card describes a specific model version, and updates change the answer.
- Write down the questions the card does not answer, and ask them of whoever is deploying the tool — a vendor, an IT department, or a school.
What the tool does
Paste what a model or system card says and get a reading: intended use, what was evaluated, stated limits, and the questions left open. It runs in this browser; nothing is sent or stored.
Limit first: This is a documentation-reading aid, not an evaluation, certification, or safety assessment of any system, and it cannot verify the claims a card makes.
Open the companion tool →One human next step
If the tool matters to a decision about a person — hiring, credit, housing, health, or school placement — ask the deploying organization for the evaluation that applies to your situation. An outside evaluation or audit report is the document to request.
Research log and safety checks
AI-assist path: not used for a verdict. This is the §1.2 UIC-10 discipline applied to documentation: the artifact reports what a card claims, what it tested, and what it omits, and never converts that into a guarantee. §6.10: not a frontier-pace topic.
§0.5 protection result: category is informed-consent-literacy; crisis-adjacent: no; fear/urgency/scarcity toolkit used: no. The protective function is free and the paid feature is convenience only.