Federal coverage is live: all 94 districts, refreshed hourly.Read the coverage notes
Product

A living matter record, with its sources attached.

Three layers of record and one layer of intelligence. Every value the product shows points back to the fetch it came from, and only the top layer is derived.

txnd · DktRpt · 14:03sha256txnd · DktRpt · 14:03sha256txnd · DktRpt · 14:03sha256txnd · DktRpt · 14:03sha256txnd · DktRpt · 14:03sha256txnd · DktRpt · 14:03sha256seqentry_datetext_rawparser_v28counselpartymatterpartycounseljudgeentry 28deadlineECF 28 · court-setApr 15, 202787 comparables60–140 GB
Intelligence
Stage, expected exit, computed deadlines, judge and counsel profiles, expected review volume. Each figure with its confidence and comparable count.
Canonical record
Source-agnostic matter, parties, counsel, judge, entries, deadlines. Every value backed by the record it came from. Confirmations in teal.
Source-normalized
One table per court system, raw strings kept, parser version recorded. Reprocessed when a parser improves; never edited by hand.
Raw record
Every fetch from the court, stored as received, immutable. The layer nothing is allowed to change.
Matter intelligence

Where the matter is, and where it is going.

Stage, days in stage, expected stage exit, next likely events, velocity, complexity, discovery intensity, expected review volume, settlement window. Each carries a confidence and the number of comparable matters behind it. There is deliberately no field for who wins.

stage: discovery
stage_confidence: 0.91
days_in_stage: 12
expected_stage_exit: 2027-02-08
next_likely_events: [order.protective, discovery.deposition_notice]
expected_gb: { p25: 60, p50: 110, p75: 140 }
discovery_intensity: high
ediscovery_trigger_at: 2026-11-24
vendor_signal: null
comparable_count: 87
as_of: 2026-09-25T14:03Z
// no outcome field. ever.
Deadlines

Computed from the entry, with the rule that produced them.

An answer due 21 days after summons returned. A 26(f) conference relative to the scheduling conference. Response windows on discovery requests. Every deadline shows its trigger entry, its rule id, and whether the court set it or we computed it.

Answer dueNov 24, 2026Computed · frcp-12-a-1-AECF 8
26(f) reportDec 5, 2026Court-setECF 28
ProductionApr 15, 2027Court-setECF 28
Dispositive motionsJun 30, 2027Court-setECF 28
Profiles

Judges and counsel, as the record shows them.

Median days to scheduling order. Motion-to-dismiss and summary-judgment grant rates. Continuance rates. Active matters. Every figure with its count. Profiles describe timing and process; they do not predict how anyone will rule.

For agents

Fourteen tools your assistant can call.

A Model Context Protocol server over the same API. Read-only toward the court, budgeted for anything that costs money, and every response marks court-supplied text as untrusted.

search_casesget_caseget_docketget_documentfetch_documentsearch_entitiestrack_matterlist_trackedget_alertswatchget_matter_intelligencecompute_deadlinesget_judge_profileget_counsel_profile

Ask the record, and see where every number came from.