- Listed available courts and judges
- Retrieved judge-specific filing rules
- Run a compliance check against those rules
1. List the courts
Start by listing the courts to see what the API covers: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
slug field when calling /rules or /check.
3. Get rules for a judge
4. Check a document
Send document metadata to the/check endpoint:
Minimal vs. full document input
Thedocument 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
Understanding results
Each result has:
The summary
status is:
COMPLIANT: No failures, no action itemsREVIEW: No failures, but action items exist (e.g. courtesy copy reminder)NON_COMPLIANT: At least one FAIL result
Next steps
- API Reference: Full endpoint reference with schemas, parameters, and live playground
- Same document, different judge: See why the same filing gets different results for different judges
- Integration patterns: How to integrate the API into your application
- Building with AI agents: Use the OpenAPI spec with LLMs