Court Rules Linter API
In May 2021, a firm filed a summary judgment motion in EDNY. The court killed it — not on the merits. The attorney filed papers before briefing was complete, violating page 3 of a 6-page standing order PDF. Same courthouse, different judge: one requires a tabbed binder with double-sided printing. The other doesn’t want paper at all. But your brief is 6 pages over their limit. The Court Rules Linter API catches that. Deterministically. Every time.What it does
Given a document’s metadata (page count, word count, structural elements) and filing context (which judge, what type of motion), the API checks compliance against three layers of rules:- Federal Rules of Civil Procedure (FRCP) — 15 rules covering signatures, captions, privacy redactions, motion requirements
- Local Rules — District-wide rules covering formatting, page/word limits, timing, and district-specific procedures
- Standing Orders — Judge-specific rules for page limits, courtesy copies, pre-motion conferences, filing gates, and bundling requirements
Key characteristics
- Deterministic — No LLM at check time. Same input always produces the same output. Sub-millisecond response times.
- Graduated input — Only
page_countandword_countare required. Provide more document structure fields to get more checks. - Three rule layers — FRCP (national), Local Rules (district), Standing Orders (judge-specific). Every result cites its source.
- Authenticated — All endpoints require a Bearer token. See Authentication.
Current coverage
| Metric | Count |
|---|---|
| Federal districts mapped | 94 |
| Districts with judge data | 20 |
| Live districts (full API access) | 1 (EDNY) |
| EDNY judges | 47 |
| Full standing order profiles | 3 (Amon, Block, Brown) |
| Curated rules | 38 (15 FRCP + 23 EDNY Local Rules) |