AI Citation Checkers Compared: What Each Tool Verifies and What None of Them Catch

On 28 July 2026 the Illinois Appellate Court fined a lawyer $15,000 for ten false items in one brief: four statutory quotations that did not exist, one case that did not exist, and five real cases that did not say what the brief claimed. Run that brief through an AI citation checker that tests whether each case exists and you catch one error in ten. The other nine pass, because the cases were real.

That ratio is why a comparison of citation checkers deserves scepticism. They check the easiest layer, and the sanctions decisions of 2025 and 2026 are increasingly about the layers they do not touch. The Illinois court: “The only acceptable standard is zero false citations”, whatever one pays for “‘premier’ or ‘corporate’ versions of AI products”.

I have not found a published head-to-head benchmark as of September 2026. What follows maps each tool’s own description, as reported in the ABA Journal’s June 2026 roundup and elsewhere, against the six error types courts punish.

Six ways a citation goes wrong, and the one most checkers test

Every AI citation checker answers some version of “does this exist?”. The Stanford study of Lexis+ AI and Westlaw counted a response as hallucinated if it was incorrect or misgrounded: a real source cited for a proposition it does not support. Charlotin’s database (2,039 decisions, 12 September 2026) counts 853 misrepresented authorities and 549 false quotations next to 1,689 fabrications.

Type 4 is the dangerous one: the checker returns green and the reader stops. The Ninth Circuit named the habit in Lnu v. Blanche (June 2026): a competent attorney “must do more than prompt generative AI, check that the citations provided by the AI are real and the subject matter roughly on point, and call it a day.”

Built into the platform: Shepard’s Verify and Deep Research Verify

Lexis+ with Protégé added Shepard’s Verify Trust Markers in May 2026. Per LawSites, they flag citations that cannot be verified as existing in Lexis content. They do not confirm that the authority supports the proposition.

CoCounsel Legal went a layer deeper. Deep Research Verify arrived in the June 2026 release notes, and the next-generation CoCounsel Legal of 20 August 2026 highlights supporting passages and flags misattributions in its Deep Research output. On paper that is type 4, though only for research the platform itself produced.

User complaints are about type 4, not type 1; one r/LawSchool poster: “Westlaw 100% hallucinates case holdings. It just may not hallucinate case names.” The platforms’ other strengths are compared in Harvey vs Legora vs CoCounsel.

The Word add-ins: Clearbrief Cite Check Report and BriefCatch RealityCheck

Clearbrief sells a Cite Check Report inside Word. LawSites covered its December 2025 launch as an audit trail for law firm partners. The published sources do not say how it handles types 3 and 4, so ask.

BriefCatch RealityCheck is described in the ABA Journal as deterministic database verification with targeted AI analysis: a database pass for existence, an AI pass for misquotes and mischaracterised holdings. The AI pass deserves caution: a model judging another model’s summary is a second opinion from the same family, and New South Wales Practice Note SC Gen 23 says verification “must not be solely carried out by using a Gen AI tool or program”.

The stand-alone checkers: Benchly, CaseRead, CiteCheck AI, CiteSentinel, GroundTruth, PelAIkan

Benchly Beyond Assure is rules-based and lives inside ezBriefs. CaseRead is free up to 50,000 characters, roughly 8,000 words. LawDroid CiteCheck AI is free for up to five documents, cross-references CourtListener and returns a colour-coded report. CourtListener matters: the Mata firm had only a limited Fastcase plan. Before pasting an unfiled brief into any free web tool, ask where it is stored and whether the vendor trains on it (see the confidentiality guides).

BrentWorks CiteSentinel charges $19.99 per document. GroundTruth is a free Word add-in. PelAIkan is the checker Damien Charlotin markets alongside his hallucination database. It is not in the ABA Journal column; its own site claims it checks “not just existence, but whether citations actually support your propositions”, which would be type 4, but that is a vendor claim and nobody has published test results, so treat it like the rest until it proves otherwise on your own brief.

In Kohls v. Ellison (D. Minn., January 2025) a Stanford expert typed “cite” as a placeholder and GPT-4o filled it with two non-existent articles; the declaration was excluded, “in a case that revolves around the dangers of AI, no less” (order). A checker should catch that, except the fakes were journal articles, which case-law databases never see.

Comparison table: form, coverage, price

Descriptions are the vendors’ own, as reported by the ABA Journal (22 June 2026), LawSites, Thomson Reuters and PelAIkan’s own site; “not stated” means unpublished.

Types 5 and 6, currency and jurisdiction, appear in no row. That is what a citator and a lawyer are for.

The error none of them catch: the real case that does not say that

In Concord Music v. Anthropic (N.D. Cal., May 2025) a Latham & Watkins associate asked Claude to produce a properly formatted citation for an article in an expert declaration. The link was correct; the author and title were wrong. The firm told the court its “manual citation check did not catch that error” (Fortune). An existence checker would have passed it.

Misgrounding is arguably more dangerous than a fabrication, because the case exists and a checker stops at existence. The Upper Tribunal in England now requires a statement of truth that every authority “(a) exists; (b) may be located using the citation provided; and © supports the proposition of law for which it is cited”. Tools do (a) and (b); only a reader does ©. The mechanism is explained in why AI makes up fake cases and, for platform tools, how RAG legal research works.

The workflow: an AI citation checker inside the six-step protocol

The LeanLaw checklist is the manual baseline: existence (30 seconds to 2 minutes per cite), holding and quotation, citator, jurisdiction, second reviewer, written record. The full protocol has its own page; here is where a checker slots in.

Step 0: extract before you check. A checker only reads what it can parse, so build the table first, in a no-training tier, with a prompt that does no verifying.

You are a litigation paralegal preparing a cite-check. From the brief below, extract every citation to a case, statute, rule or secondary source into a table: Citation as written | Page of the brief | The sentence it supports (quoted) | Any quotation attributed to it (verbatim) | Verification status.
Set every status to "NOT YET VERIFIED". Do not assess whether any citation is real, current or accurate; do not correct or reformat anything. Copy ambiguous citations as written and add "[INCOMPLETE]".

Brief:
[paste]

Step 1: run the checker. Flagged items go first; unflagged items still get read.

Step 2: read the pin cite yourself in Westlaw, Lexis, CourtListener, BAILII or juris. A model can then help compare wording, provided the passage comes from the database, not the model’s memory.

Below is a sentence from my brief and the passage from the cited opinion, copied from the official database at the pin cite. Answer: (1) Does the passage support the sentence fully, partly or not at all? Quote the words that decide it. (2) Is any quotation in my sentence verbatim in the passage? Show every difference. (3) Is the passage holding, dicta, a party's argument, or a quotation from another case? Use nothing outside the two texts; if insufficient, say "PASSAGE INSUFFICIENT".

My sentence:
[paste]

Passage from the opinion, with pin cite:
[paste]

Step 3: citator, jurisdiction, record. KeyCite or Shepard’s for status, your own judgement on jurisdiction, then a log entry naming who checked what and when; Legal AI Governance lists a pre-filing verification log among the artefacts to have ready at insurance renewal, and courts from N.D. Texas to the Upper Tribunal now ask you to certify the check. The Nebraska Supreme Court’s line in Prososki v. Regan: “It does not matter if [generative AI] told you so.”

Step 4: check the other side. In Noland v. Land of the Free the California Court of Appeal denied the respondents their fees because they “did not alert the court to the fabricated citations”. A $19.99 pass over an opponent’s brief is now part of the job.

Act as a sceptical appellate clerk. List every authority cited in the brief below and flag these red flags: reporter or volume number wrong for the year; implausible page number; unusual docket number; a court that did not exist on the stated date; a case name that reads like a description of the argument; a holding stated without qualification; a quotation without a pin cite. Output a table: Citation | Red flags (or "none") | Priority for human verification | Database to check. Do not say whether any case is real; I will check every one.

Opponent's brief:
[paste]

The verification session of AI Lab for Lawyers does exactly this: the same brief through two checkers, then the hunt for the error neither flagged, which is nearly always a real case cited for the wrong proposition.

Where to go next: the six-step verification protocol is the baseline these tools accelerate; what to do when you find a fake citation covers the 48 hours after a checker lights up red; the verification hub has the rest, and the prompts are in the prompt library.