Build against verified law.

Verdict verifies citations, quotes and whole briefs against a corpus of public court records, and returns every answer inside a Trust Envelope: the sources it used, the verification labels with their evidence, the coverage it had, whether attorney review is required, and an audit record you can pull back later.

The honesty contract

These rules are load-bearing. They are the reason a verification result is safe to build on, and they are quotable in your own user-facing copy.

  • A coverage gap is never called a fabricationWhen the corpus cannot decide, you get an honest gap label — explicitly not evidence of fabrication.
  • Every accusation carries its evidenceA fabrication-class label quotes what was checked and what was found, down to naming the case a mis-cited page falls inside.
  • Absence of a treatment signal is never clearanceclearance is schema-constant false. Nothing here tells you a case is good law by omission.
  • Refusal over accusation on damaged sourcesIf the official scan is OCR-damaged or unextractable, quote checks refuse to rule rather than accuse.
  • We measure our own accusation labels and publish the numbersWhere a label's measured precision does not support blocking, the guidance says so — and your gate should read it rather than guess.

What is in the corpus

Three different measures, easy to conflate — so here they are separately. Live coverage by jurisdiction is a free call to GET /v1/coverage, and every response states its own coverage.corpus_as_of.

10M+
cases resolvable — what a citation-existence check runs against
~4.5M
full-text opinions — the base a quote check is grounded in
65M+
citation-graph edges between those cases

Public court records, including the Caselaw Access Project. Citation parsing uses eyecite.

Two ways in

The same 13 tools over REST for software, or over MCP for agents. Both take the same Bearer token — an API key or an OAuth access token.

# REST
curl -X POST https://api.verdict.io/v1/citations/verify \
  -H "Authorization: Bearer $VERDICT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "Brown v. Board of Education, 347 U.S. 483 (1954)"}'

# MCP
https://mcp.verdict.io/mcp

A citation check costs 3¢, and 1¢ when we return an honest coverage gap — we charge less when we cannot answer definitively. Reading back an audit record is free. See pricing.

Send your text exactly as published

Do not canonicalize citations before sending them
Accusation evidence quotes your payload back to you. A consumer-side rewrite — citation canonicalization, glyph substitution — makes the evidence cite text that is absent from your source, and a local shim silently masks upstream grammar fixes. Stripping markup is fine; rewriting citations never is. If a citation form goes unrecognized, report it with a controlled pair (one fabricated, one real) and the grammar gets fixed for every consumer at once.

Next

The 13 tools — what each one does, its REST route and what it costs.
Label semantics — the part integrators get wrong, and how to gate on it safely.
MCP server — connecting an agent, and the rate, replay and pinning contract.

The machine-readable twin of these pages is served at the consumer guidance endpoint. Where they disagree, the served guidance wins.