SafetyPage

How it works

SafetyPage is a library of the AI safety record: research papers, system cards, safety frameworks, evaluation reports and government guidance. Every search result opens an exact page or paragraph. Every citation names a document, a version and a place in it, and code can check it against that place.

It holds 13,898 documents on 7 shelves: 165,940 PDF pages and 487,637 paragraphs of web documents, each one citable. 3,505 documents are openly licensed and read in full here; the other 10,393 are searched, cited and quote-checked here and read at their source.

What a citation is

arxiv:2305.15324/v2/p6 is a document, a version and a page. The version is always there, because pages move when a paper is revised. The same three parts make the link: /d/arxiv/2305.15324/v2/p6.

How a quote is checked

The check is deterministic and uses no model. The quoted words have to be on the cited page, in order, with no words skipped, starting and ending on whole words. Case, punctuation, hyphenation across line breaks and ligatures are forgiven. A dropped “not” is not: a quotation one word away from the page fails, and the result shows the page's own wording.

A citation is shown in one of three states. Verified means the quoted words are on the cited page. Page only means the page is real and there was no quote to check. Rejected means anything else, with the reason. A rejected citation is struck through, never hidden.

The check says whether the page contains the words. It does not say whether the page supports the claim made about it. Where a model judges that, its verdict is labelled as a judge's and kept apart from the code's.

Licences

Documents under an open licence (CC BY, CC BY-SA, CC0, public domain, the UK Open Government Licence) are hosted in full, and their record shows the evidence for the licence. Everything else, and anything whose licence we could not find, can be searched, cited and quote-checked here, and opens at its source at the cited page. The tier changes where you read a document, not what the library knows about it.

How it is built

The text of record is the PDF's own text layer. No model transcribes a document. The reader, the checker, the MCP server and the benchmark all use one implementation of each rule, so a verdict an agent gets during a run is the verdict the leaderboard scores. The library is served from frozen snapshots; a benchmark names the snapshot it ran against.

The design, with the decisions behind it, is in the architecture document. The code is Apache-2.0.