Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Legal research, grounded in real cases
Cohesive360 exposes the CourtListener public-record case-law and PACER docket database to Claude through 8 read-only tools across 5 capability areas. Search opinions, resolve citations, read full docket histories, look up courts and judges — all citations link back to the source so nothing is taken on faith. Free public data behind every search; the connector layer keeps Claude grounded.
Public case law, on call
Decades of federal and state opinions, dockets, and judge bios — searchable in plain English. Claude can pull holdings, summarise dockets, or surface relevant precedent without leaving chat.
Free and open by mandate
CourtListener is run by the Free Law Project — public-record data, no paywall, no per-query fees. Your firm pays for our connector, not for the underlying data.
Read-only by design
This connector has zero write tools. There's nothing to draft, approve, or roll back — Claude can only research and report. The classic 'AI made up a case' failure mode is the one we engineered against most explicitly.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
5 workflow areas. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Full-text search across CourtListener's opinion corpus and PACER docket archive. Filter by court, date range, party, case number, and natural-language query terms.
Full-text search across CourtListener's opinion corpus and PACER docket archive. Filter by court, date range, party, case number, and natural-language query terms.
What you can ask Claude
- “Find Ninth Circuit opinions citing Twombly from 2023 about Section 230”
- “Search PACER for active patent cases involving Acme Corp in the District of Delaware”
- “Pull state-court decisions on uninsured-motorist coverage from New York after 2020”
- “Any recent class actions where the lead plaintiff is Smith v. anyone”
Underlying tools (1)
searchResolve any citation — federal, state, regional reporter — to its canonical case record. Useful for fact-checking a brief, expanding a string cite, or finding the parallel reporter.
Resolve any citation — federal, state, regional reporter — to its canonical case record. Useful for fact-checking a brief, expanding a string cite, or finding the parallel reporter.
What you can ask Claude
- “What case is 550 U.S. 544”
- “Resolve the citation 2023 WL 4567890 to a full opinion”
- “Find Smith v. Jones, 123 F.3d 456 (9th Cir. 1999) on CourtListener”
Underlying tools (1)
lookup_citationPull full opinion text, docket entries, party lists, attorneys of record, and metadata for any matter CourtListener has indexed. Backed by clusters (opinion groupings) and docket records.
Pull full opinion text, docket entries, party lists, attorneys of record, and metadata for any matter CourtListener has indexed. Backed by clusters (opinion groupings) and docket records.
What you can ask Claude
- “Get me the full opinion text for cluster 1755433”
- “Pull the docket on Smith v. Jones in NDCA, every entry since filing”
- “Read the full Roe v. Wade majority opinion verbatim — I need to quote a passage”
- “Who were the attorneys of record on Acme v. Initech”
Underlying tools (3)
get_opinionget_clusterget_docketList the federal and state courts CourtListener indexes — useful for sanity-checking jurisdiction and getting the canonical court identifier before scoping a search.
List the federal and state courts CourtListener indexes — useful for sanity-checking jurisdiction and getting the canonical court identifier before scoping a search.
What you can ask Claude
- “List every federal district court in the Second Circuit”
- “What's the CourtListener identifier for the Southern District of New York”
- “Show me California state appellate courts”
Underlying tools (1)
list_courtsLook up judges — biographical details, appointing president, bench tenure, opinion history. Handy for prep on motion-day, depositions, or any time you want to know who's deciding.
Look up judges — biographical details, appointing president, bench tenure, opinion history. Handy for prep on motion-day, depositions, or any time you want to know who's deciding.
What you can ask Claude
- “Find Judge Sotomayor's bio and bench history”
- “Search for federal judges named Wilson sitting in California”
- “Get the full record on Judge Smith of EDNY”
- “Who appointed Judge Wilson and when did he take the bench”
Underlying tools (2)
search_judgesget_judgeLimits and roadmap
What the CourtListenerconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- PACER document downloads (full-text PDFs). CourtListener indexes PACER docket metadata broadly but the actual PDF documents on PACER are per-page paid. The connector returns docket entries and links; to retrieve the underlying PDF you'd pay PACER directly through the link.
- Briefs and motion text outside opinions. CourtListener surfaces opinions and select RECAP-archived docket entries; briefs, motions, and discovery filings aren't comprehensively indexed. For full briefing histories, the underlying PACER docket is the source.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Secondary-source research (treatises, hornbooks, ALR). CourtListener is primary-source case law and dockets. For Westlaw-class secondary materials, the vLex (Fastcase) connector is on the roadmap.
- Filing or e-filing motions. Filing is court-specific and ECF-portal-bound — out of scope for a research connector. This will always be read-only.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Read-only connector
Zero write tools. There's nothing here that can change anyone's case record, alter a docket, or push a filing — CourtListener is a research database, and the connector mirrors that.
Per-user API key in encrypted vault
CourtListener provides a free API key tied to each user's account. We store yours encrypted with AES-256-GCM, master key in Azure Key Vault, ciphertext bound to your user ID — never in logs, never echoed in responses.
Citations link back to the source
Every search result Claude surfaces includes the underlying CourtListener URL so you can verify the citation, read the full opinion, and confirm Claude didn't misread or hallucinate the holding.
No hallucinated cases
Claude only knows about cases CourtListener returns from a real search. The connector instructions explicitly tell Claude to refuse generating citation strings without a search-grounded source — closing the classic 'made-up case' failure mode.
What CourtListener via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your CourtListenertenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.