Skip to main content
Court Rules has two kinds of data. Court rules are the filing rules of federal district courts and state trial courts, down to the judge or courtroom. Enforcement data is privacy enforcement events from the FTC and state regulators. The quickstart covers court rules via the REST API, and it ends with a compliance check, which runs for the Eastern District of New York. To read the rules of any other court, see Read a court’s rules. For enforcement data, see Enforcement data and MCP: enforcement data. By the end of this quickstart, you will have:
  • Listed available courts and judges
  • Retrieved judge-specific filing rules
  • Run a compliance check against those rules
All from your terminal in under 5 minutes. The guide walks through four calls: discover courts, list judges, get applicable rules, and check a document. All requests require a Bearer token. See Authentication for details.

1. List the courts

Start by listing the courts to see what the API covers:
Every court is open to any API key. Courts with status: live have rules you can read with /rules and /extracted-rules, state courts included. Compliance checks (step 4) run for edny today; for other courts, /check returns 422 and points you to their rules. The list is long, and each court in it counts as one row against your daily row limit, so call it once and keep the result. To read one court, call GET /api/v1/courts/{district_id}. Rate limits explains how rows are counted, and Coverage explains how to check how deeply a court is covered.

2. List judges in a district

Returns all judges for the district. Use the slug field when calling /rules or /check.

3. Get rules for a judge

Returns the full rule set organized by authority layer: FRCP, Local Rules, and Standing Order.

4. Check a document

Send document metadata to the /check endpoint:

Minimal vs. full document input

The document object only requires page_count and word_count. With just these two fields, the API checks:
  • Page and word limits (judge-specific and local rules)
  • Courtesy copy requirements
  • Pre-motion conference requirements
  • Filing gate and bundling rules
To get structural checks (caption, signature, required sections), provide the optional fields. See Document structure for the full schema.

Understanding results

Each result has: The summary status is:
  • COMPLIANT: No failures, no action items
  • REVIEW: No failures, but action items exist (e.g. courtesy copy reminder)
  • NON_COMPLIANT: At least one FAIL result

Next steps