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
0 workflow areas in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Limits 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.