Skip to main content
The verification tools check scientific writing before anyone relies on it. They work on text from any source: a model’s own draft, a user’s manuscript, or citations recalled from memory or found by web search. You don’t need to have found the sources through Scite. Requires a Scite premium subscription.

The verification loop

The server’s instructions tell connected models to run this loop on any scientific answer before returning it:
1

Check the claims

Call check_claim on each substantive claim to pull the verbatim statements for and against it. Drop or flag any claim nothing supports.
2

Check the citations

Call verify_papers on every DOI or reference about to be cited, wherever it came from.
3

Record the decisions

Call report_citations once with every source cited and every source considered and dropped, each with a reason and its provenance. Call citation_report to show the include/exclude record.
bibliography then formats the final reference list from stored metadata rather than from memory.

check_claim

Pass up to 20 claims as plain statements. For each one, check_claim returns the sentences in the literature closest to it, labeled by source, with the retraction and dispute status of each paper.

Parameters

What it returns

Each claim gets a result with these fields: The summary counts are not a verdict. A keyword match isn’t entailment, so confirm each quote actually states the claim before relying on it.
To get the claim’s citation graph in one call, pass the claim to citation_graph as claim instead of calling both tools.

verify_papers

Pass up to 20 references per call, as bare DOIs, references as written, or a mix. Each one comes back verified with the matched record, or could_not_verify with a reason.
A verified reference can also carry: could_not_verify means Scite couldn’t confirm the paper exists, either in its records or at doi.org. It doesn’t mean the paper is fake. Check it before citing.

report_citations

report_citations records an answer’s full source decision set: every source it cited and every source it considered and excluded. Call it once per answer.
Each item in citations takes: Pass an optional answer_id to group decisions, and context for the question or inclusion criteria. source records provenance honestly. Confirming a citation with verify_papers doesn’t make its source scite_mcp. The response returns recorded_cited, recorded_excluded, skipped (malformed items), and the accepted decisions as cited[] and excluded[]. When a cited DOI that didn’t come from Scite is retracted, withdrawn, or under an expression of concern, the response adds editorialAlerts and a message.
For organizations with no-retention handling of query text, reason, reason_code, source_detail, context, and any non-DOI source_ref are not stored. In the Scite Assistant, decisions appear in the answer’s fact-check panel and are not stored, so citation_report has nothing to summarize there.

citation_report

citation_report summarizes the decisions recorded with report_citations for the current session, or for one answer_id. It’s read-only. It returns the identified, screened, included, and excluded counts (retrieved is null for an answer-scoped report), excluded_by_reason, by_stage, by_source, checks (such as decisions missing a reason), truncated, and the full included[] and excluded[] lists. That’s the screening funnel a PRISMA flow diagram or a regulatory evidence submission needs.

bibliography

bibliography formats papers you’ve already found as a reference list built from Scite’s stored metadata, so keys and fields are exact.
For Zotero, Mendeley, or ReadCube Papers use ris or bibtex; for EndNote use enw. apa returns an APA 7 list ready to paste into an answer, covering journal articles only. The response carries format, found, notFound, and content. A DOI that matched only after dropping trailing punctuation is listed in corrected.