CourtListener / RECAP search results land directly onto disk in raw JSON format before parsing. A cryptographic SHA-256 digest is generated immediately, establishing an immutable provenance trail for enterprise evaluation.

Every row below represents an actual network landing from the Free Law Project CourtListener RECAP API. Checksums can be validated against the local snapshot JSON files on disk.

These JSON endpoints power this UI and can be queried directly via curl or integrated into external ETL pipelines:

# 1. Search patent cases in D. Delaware
curl "http://localhost:4100/api/v1/cases/search?ipType=PATENT&court=ded&limit=5"

# 2. Free-text search by party or patent number
curl "http://localhost:4100/api/v1/cases/search?q=patent&limit=10"

# 3. Retrieve immutable raw audit snapshots with SHA-256 hashes
curl "http://localhost:4100/api/v1/snapshots"

# 4. Pipeline volume statistics by IP litigation classification
curl "http://localhost:4100/api/v1/stats"

Every case below was auto-ingested and auto-classified successfully, but landed here because at least one field genuinely cannot be filled in responsibly by code alone: case outcome (who prevailed requires reading the actual order or judgment, not just docket dates), or a patent-in-suit number that shallow caption/snippet regex couldn't find. This is the exact class of work Darts-ip pays expert analysts to do — a review submitted here is written back to the structured record with a “Human-Verified” badge, visible in the Docket Explorer.