Frequently Asked
Questions
Everything authors, lab directors, and peer reviewers ask about deterministic citation auditing.
How does StrictCite verify references without reading my paper? +
All document segmentation runs 100% locally inside your browser RAM. When you paste text or upload a .bib file, StrictCite’s client-side regex engine isolates only the reference list strings.
Your manuscript prose, hypotheses, data, and equations never leave your computer. The engine only sends public DOI/title strings ephemerally to open academic registries (Crossref/PubMed) to confirm their existence.
Which academic databases and registries are queried? +
Thirteen, queried directly from your browser. Four are the agencies that issue identifiers — Crossref, DataCite, doi.org and Open Library — and are asked first.
What is a "hallucinated reference" and how do you detect it? +
Generative AI tools (ChatGPT, Claude, Copilot) frequently invent fake references: they generate real-sounding author names, valid journal titles, and fabricated DOIs that do not exist.
StrictCite resolves every identifier against the registry that issued it. If a cited DOI returns a HTTP 404 Not Found in official publisher records, or if the title text fails fuzzy similarity scoring against the canonical record, it is flagged as a suspected hallucination.
Does StrictCite integrate directly with Overleaf, Zotero, and LaTeX? +
Yes! StrictCite produces standardized, normalized native exports:
- — .bib: Cleans syntax, standardizes citation keys, adds missing DOI & ISSN fields for direct Overleaf upload.
- — .ris: 1-click import into Zotero, Mendeley, and EndNote.
- — .json: For modern web bibliographies and Quarto/Pandoc pipelines.
- — .bbl: Accepted and repaired field by field.