What a Wizzad record is
Someone has shown you a link to their Wizzad record, or a credential from it. This page says what you are looking at, what it can tell you, and what it cannot.
In one sentence
A Wizzad record is a signed account of what a student did in Wizzad: which questions were put to them about a piece of their own work, how their answers were checked, and what was recorded while they answered. Every attempt is kept, in order; a later attempt never replaces an earlier one.
How a record comes to exist
A student writes a piece — an essay, a lab write-up, an application essay — in Wizzad, or brings one in as a file. Then they defend it: a timed session in which Wizzad puts questions to them that are built from the piece itself, with the piece out of sight. Some questions have an answer that is taken straight from the piece and compared automatically; some ask for an explanation in the student's own words, which two separate AI graders read against a marking guide; some ask about a change the student made while writing, which only they would know. The results are counted and fixed at the time, and the whole thing is signed.
A reader of the record can also ask the student one question back, ask them to sit a short fresh check on a piece, or set them a new task to make in Wizzad and defend. Whatever happens appears on the record, signed on its own, and only then.
What it tells you
- How many questions were asked about each piece, and how many were answered correctly or explained fully — with the questions and answers behind the numbers, when the student chose to include them.
- When each attempt happened, how long it took, and whether the student left the window or pasted text during it (counted, never policed).
- For a piece written in Wizzad, how it was made: how many sittings, how much was typed, pasted, or written with Wizzad's assistant.
- For a piece brought in as a file, the file's fingerprint — so if you hold a copy, you can check it is the same file.
- How the student was identified in each session: a signed-in account, or a passkey at the start.
What it does not tell you
It does not establish who wrote any piece, whether AI was used in writing it, or who the student is. Nothing in it is a verdict, a comparison with other students, or an examination result. The name on a record is the name the student typed; Wizzad has not checked it.
Read the record for what it is: evidence that whoever sat that session, at that time, could answer for that piece of writing without it in front of them — no more, and no less.
What "valid" means
Valid means two things, and only two: the record's contents are exactly what Wizzad signed — nothing was changed afterwards — and the signature was made with a key Wizzad publishes as its own.
It does not mean the person showing you the record is the student it describes; the record's own identity lines say how far that goes. And it does not mean the claims are true in any larger sense — only that Wizzad's software recorded them at the time.
Three ways to check a record
- On Wizzad
- Every record page has a Check this record button. It takes a few seconds and needs no account.
- Here, in your browser
- Paste the record's link on the check page. It fetches the record and Wizzad's public key and checks the signature on your machine, with none of Wizzad's code involved.
- On your own computer
npx wizzad-record check <link>does the same from the command line, and can also check a credential or a file you hold.
Credentials
When a reader sets a student a task and the student finishes and defends it, Wizzad issues an Open Badges 3.0 credential for it — the same open format universities and employers use for digital badges. It names the task as it was set, the counts from the defense, and how the piece was made, and it is signed like the record. Verifiers that support Open Badges 3.0 can check it, and so can the command line above.
Who made this page
This checker is published by Wizzad as open source, on purpose: a record you can only check by asking Wizzad would be worth less. Engineers can read the exact profile — the signing, the keys, the credential format — in the technical profile.