CourtListener: what it returns, and whether it works in Clay
CourtListener is not available in Clay. It is best for Diligence, Buying signals. Pricing: Free. Access: Free API with a token, alerts and bulk data. Default limits are low (reported 5 per minute and 125 per day since May 2026, not confirmed on the page checked); higher limits with membership or a commercial agreement..
Data domains: Legal, Corporate events, Signals.
What does CourtListener return?
Official fields: docket id; court; docket_number; case_name; date_filed; date_terminated; date_argued; pacer_case_id; nature_of_suit; clusters; cluster citations and judges; opinion type; plain_text; html_with_citations; download_url; opinions_cited. Party, attorney and cause fields on federal dockets were not confirmed in the pages checked.
What can you derive from it?
1. Litigation exposure: new dockets naming a company show legal pressure, for example privacy, ADA website or wage claims. 2. Category hotspots: nature_of_suit counts by industry show where a compliance problem is spreading. 3. Serial plaintiffs: repeat filers in one category predict who gets sued next. 4. Case resolution: date_terminated shows when a matter closed.
How would a GTM team use it?
1. Revenue trigger: alert on new website accessibility or data privacy suits and offer remediation from a compliance portco. 2. Market map: chart filings by nature of suit to size a compliance problem by sector. 3. PE screen: check litigation history of add-on targets before outreach. 4. Competitive watch: track suits involving competitors, such as patent claims.
What are the caveats?
Not a native Clay integration as of 2026-10-17 (checked against Clay's integrations catalog). Can be called through Clay's HTTP API column where an API exists. External observation: a lawsuit shows exposure, not that the company will buy anything. Federal docket coverage depends on what RECAP users have pulled from PACER, so many dockets are partial. State court coverage is limited. Name matching to companies needs review.