Legal and case-law research
Mit CourtListener-Endpunkten verwandelst du legal and case-law research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn CourtListener's free legal database into structured JSON — full-text search across published court opinions with normalized result metadata, and a browsable directory of U.S. courts, all from CourtListener's anonymous public search.
Search CourtListener's public court-opinion index and browse its court directory as structured JSON, for legal and case-law research.
Endpunkt-Familien
3
Dokumentierte Parameter
9
Beispiele
3
Live-Katalog-Snapshot
Aktive Endpunkte
3
Methoden
GET
Pflichtparameter
4
Schema-Referenzen
3
{
"platform": "CourtListener",
"endpoint": "courtlistener-courts",
"method": "GET",
"path": "/courtlistener/courts",
"auth": "apiKey"
}Use Cases
Search CourtListener's public court-opinion index and browse its court directory as structured JSON, for legal and case-law research.
Mit CourtListener-Endpunkten verwandelst du legal and case-law research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit CourtListener-Endpunkten verwandelst du court opinion monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit CourtListener-Endpunkten verwandelst du litigation and compliance intelligence in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-CourtListener-Endpunktkatalog — 3 Endpunkte, 9 dokumentierte Request-Parameter und 3 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
3 documented CourtListener endpoints, grouped into 3 request families — Courts, People and Search.
9 request parameters are documented across those CourtListener endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 CourtListener endpoints ship a recorded example response, and 3 carry a documented response schema — you can code against the real JSON before the first request.
CourtListener endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
3 hosted MCP tools back the CourtListener endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/courtlistener/courts
/courtlistener/people
/courtlistener/search
Endpunktkatalog
/courtlistener/courtsLists CourtListener's anonymous public court directory. Provide court_id to retrieve one court. page is used only for directory browsing and is 1-indexed. The endpoint does not retrieve dockets, opinions, judges, or account data.
MCP-Tool courtlistener_courts
/courtlistener/peopleLists CourtListener's anonymous public judicial-person directory. Provide person_id to retrieve one public person record. The response contains only public directory and position-summary metadata; sensitive biographical fields are excluded.
MCP-Tool courtlistener_people
/courtlistener/searchSearches CourtListener's opinion-search index by text and returns opinion-result metadata with a cursor for the next page. The endpoint does not return opinion detail, dockets, judges, alerts, or account data.
MCP-Tool courtlistener_search
Verwandte APIs
Business & Market Intelligence
Turn public GitHub ecosystem signals into structured data for developer-market research, open-source intelligence, recruiting, and AI-agent workflows.
Business & Market Intelligence
Collect public TrustMRR startup marketplace and leaderboard data as normalized JSON for startup research, SaaS discovery, and market intelligence workflows.
Business & Market Intelligence
Add website and competitive intelligence signals from SimilarWeb to research pipelines.
So scrapst du CourtListener
CourtListener publishes court opinions and a court directory as anonymous public search data. Crawlora's CourtListener endpoints return normalized results as JSON with one API key — no scraper or search-index client to maintain. A pull on 2026-10-27 showed the court directory at 3,359 courts, 20 per page, and the people directory paging by an opaque cursor.
Send a text query to /courtlistener/search for normalized opinion-result metadata, with a cursor to page through further results.
Call /courtlistener/courts to list CourtListener's public court directory, or pass court_id to retrieve one specific court's detail. page is 1-indexed and used only for directory browsing.
The courts route returned a total of 3,359 courts with 20 per page and a next_page value. Rows carry an id such as scotus, a short and full name, a citation abbreviation, a position and in_use and has_opinion_scraper flags, so filter on those flags before assuming a court's opinions are collected.
The people route returned 20 judges per page with an id, slug, profile URL and position_count (Cynthia Aaron, id 6300, had one recorded position), and a next_cursor to continue. Keep the cursor opaque and store the retrieval time, because the directory changes as records are added.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft CourtListener-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken CourtListener ab:
Researches public US legal opinions, courts, and judicial people through CourtListener via the Crawlora API, returning clean JSON. Use when the user…
npx skills add github.com/Crawlora-org/crawlora-skills --skill courtlistener-researchFAQ
Send a text query to Crawlora's /courtlistener/search endpoint and get normalized opinion-result metadata back as structured JSON, with a cursor to page through additional results — no need to build your own legal search index.
No — CourtListener endpoints use CourtListener's anonymous public opinion-search and court-directory data only. They do not retrieve authenticated opinion detail, dockets, judges, alerts, or account data.
Collecting publicly accessible opinion-search and court-directory data is generally permissible if you respect CourtListener's terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.
3,359 courts on 2026-10-27, returned 20 at a time. Use the in_use flag to separate current courts from historical ones.