Guide
Understanding your report
Every scan produces the same underlying evidence, offered in a few different shapes depending on who needs to use it and how. Here's what each one is actually for.
HTML report
For a person making the call
Open it in your dashboard when you need to actually read the evidence — the classification badges, what was checked, what wasn't found. This is the format for a reviewer weighing a decision, not for handing to a system.
Who uses it: An academic-integrity reviewer walking through a disputed submission. An agency lead checking an asset before it ships.
Shareable public link
For handing to someone outside your team
An unguessable link to the same report, viewable without an account. This is the actual client-facing deliverable — send it alongside an asset as "here's what we checked," or reference it in a hearing without giving anyone dashboard access.
Who uses it: An agency delivering an asset to a client. An academic-integrity panel citing evidence in a decision.
It's a live link, not a fixed record — revoking it later makes it stop working. If you need something permanent and unrevocable, that's what PDF is for (see below).
JSON export
For feeding into another system
The same evidence and assessment data, structured for a machine rather than a person — every classification, every claim key, the full assessment. Built for piping into your own queue, dashboard, or audit log rather than reading directly.
Who uses it: A trust & safety team routing scan results into their own moderation pipeline. A compliance team archiving a machine-readable record per asset.
This endpoint has no authentication yet and there's no API product shipped — today it's reachable with direct backend access, not something to hand an external integration partner. Treat it as a preview of where this is going, not a live integration point.
PDF export
For the permanent, fixed record
A static file you can attach to an email, a case file, or a formal response — the record of last resort when something needs to exist independent of the app, unrevocable and unchangeable.
Who uses it: An agency attaching evidence to a client contract file. An academic-integrity office filing evidence with a student's case record.
Not built yet. Until it ships, an authenticated user can print the HTML report to PDF directly from the browser — a manual workaround, not a feature.
One more thing
None of these are a verdict
Whichever format you're looking at, it's evidence for a person to weigh, not a decision Provenance Radar has already made for you. A classification badge tells you what was checked and how certain it is, never whether the content is acceptable to publish, submit, or ship.