Grey Matter is in private preview.Request access
Product

A living matter record, with its sources attached.

Three layers of record and one layer of intelligence. Values point back to the fetch they came from; 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-setFeb 1, 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. Each 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; not edited by hand.
Raw record
Each 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, expected exit, expected review volume, discovery intensity, when discovery opened, and whether a vendor is named. Each carries a confidence and the number of comparable matters behind it.

Halvorsen v. Meridian
Matter intelligence · as of Sep 30, 2:03 pm
N.D. Tex. · 4:26-cv-00812
StageDiscovery · day 22confidence 0.91
Expected stage exitFeb 17, 2027 · ~140 daysmedian of 87 comparables
Expected review volume60–140 GB · p50 11087 comparables · N.D. Tex. · contract
Discovery intensityHighmotion to compel within 14 days of the order
Discovery openedSep 8, 2026ECF 28 · scheduling order
VendorNone namedno ESI protocol on the docket
What usually happens next

A protective order in 71% of comparable matters, then a first deposition notice a median of 96 days after the scheduling order.

Example matter. Parties, counsel and figures are invented for illustration.

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.

Response to motion to compelOct 13, 2026Computedfrcp-6-b · ECF 31
Reply in support of motion to compelOct 27, 2026Computedlr-7.1-e · ECF 31
ProductionFeb 1, 2027Court-setECF 28
Dispositive motionsApr 15, 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. Each figure with its count.

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. Court text is quoted, never obeyed.

search_casesget_caseget_docketget_documentfetch_documentsearch_entitiestrack_matterlist_trackedget_alertswatchget_matter_intelligencecompute_deadlinesget_judge_profileget_counsel_profile

One record, from the raw fetch to the deadline on your calendar.