Case Watch
Persistent monitoring of federal matters for new docket activity.
Re-checked about every 6 hours; alerts by email.CaseMagic turns fragmented court records, case events, correspondence and litigation relationships into persistent, structured intelligence that lawyers, businesses and AI agents can use.
Federal litigation is the wedge. The Litigation Knowledge Graph is the platform.
Counted from production. Revenue and customer figures are shared in the investor deck.
The record of a single lawsuit is scattered across systems that were never designed to talk to each other, and none of them was designed to be read by an AI agent.
One persistent, structured record per matter, with identity and context an agent can call.
AI agents can reason about litigation only when litigation has persistent structure, identity and context.
Courts create the authoritative litigation record. Lawyers and litigants create the private matter record. AI agents need structured, persistent access to both. CaseMagic connects them.
Solid: in production. Dashed: being built with this round.
Court events happen whether or not anyone opens the software. That makes litigation a recurring data stream, and a monitored case a recurring reason to come back.
↺ and back to step 01, with more context than the last pass.
Court documents can be replicated. A continuously enriched litigation graph that combines public records, private matter context and agent interactions is designed to become progressively harder to reproduce. That is the defensibility we are building, not one we claim to have finished.
Each one is live at casemagic.ai today. The interface fragments below are drawn from the product; the case shown is illustrative.
Persistent monitoring of federal matters for new docket activity.
Re-checked about every 6 hours; alerts by email.Persistent, structured identity and context for each matter.
One record per matter that survives a change of hands or assistant.Private correspondence connected directly to the matter.
A permanent address per case; messages and attachments filed to it.Continuous discovery of newly filed federal litigation from reusable criteria.
Read from 88 district courts’ own filing feeds.Structured litigation access for AI assistants and applications.
17 MCP tools, listed in the official MCP registry.Every step below runs in production. Check a real case free; it takes under a minute.
AI assistants are not competitors to CaseMagic. They are where people already ask about their cases, and each one that can call CaseMagic is a channel that brings users to the record.
CaseMagic app in ChatGPT; real lookups from ChatGPT’s own client recorded in production.
Remote MCP with OAuth, PKCE and dynamic client registration, run end to end against production.
Gemini called CaseMagic’s check_case function and answered from live docket data.
The free lookup runs over the stateless MCP transport xAI documents.
Same MCP and OAuth shape as Claude; not yet connected from Muse itself.
“What changed in Acme Corp. v. Smith?”
get_case_updates · the docket, new filings, deadlines, parties, correspondence and the Case Passport
With structured, current litigation context, and a link back to the case in CaseMagic.
The user discovers CaseMagic through the agent. Every link an assistant prints carries a signed source, so a customer who arrives through ChatGPT is credited to ChatGPT in our attribution, not to “direct”.
Statuses come from the compatibility record behind the integrations page: “Live” means real use from that assistant’s own client has been recorded; “Verified over MCP” means the protocol path has been run end to end against production.
Revenue, customer and retention figures are in the investor deck. What is public is the system itself, and how fast it was built.
People increasingly expect an assistant to reach into specialized systems for them, not to be pasted into.
Institutional capital has validated legal AI as a major software category. The data layer under it is still open.
The Model Context Protocol lets ChatGPT, Claude and other assistants invoke external structured services with the user’s permission.
The authoritative litigation record remains structurally hard for a general-purpose AI to monitor persistently.
Built bottom-up from who pays for each layer, not from one speculative TAM figure.
Self-represented litigants and small practices with active federal matters, paying monthly per monitored matter.
Plus paralegals and litigation support, per the ABA’s national lawyer population count, on the higher-priced plans.
Law firms, corporations, insurers, financial institutions, compliance teams, litigation finance and legal software vendors.
Software and AI agents consuming litigation intelligence through the API and MCP, priced on usage.
Expansion beyond the wedge: state courts, then administrative and regulatory proceedings, on the same data model.
A monitored case is a subscription that lasts as long as the litigation. Expansion comes from more matters per account and from higher tiers.
$99per month, live today
One monitored matter.
$299per month, live today
Up to 10 monitored matters.
$599per month, live today
Up to 50 monitored matters.
Contractusage-based, planned
For firms, companies and applications calling the API at volume.
Legal AI assistants reason over what they are given. Practice-management software organizes a firm’s workflow. Court databases provide documents and dockets. CaseMagic maintains the persistent, structured litigation context that people, applications and AI agents can keep reading.
| Capability | CaseMagic | Docket monitoring | Practice management | Legal AI assistant | Public court database |
|---|---|---|---|---|---|
| Persistent monitoring | Yes | Yes | No | No | No |
| Private correspondence context | Yes | No | Yes | Partly | No |
| Persistent matter identity | Yes | Partly | Yes | No | Partly |
| Litigation knowledge graph | Building | No | No | No | No |
| AI-agent access | Yes | No | Partly | Yes | No |
| API / MCP | Yes | Partly | Partly | No | Partly |
| New-filing discovery | Yes | Partly | No | No | Partly |
| Cross-case intelligence | Building | No | No | No | Partly |
| Public + private context together | Yes | No | No | No | No |
| Actionable alerts | Yes | Yes | Partly | No | No |
Categories, not named products. “Building” marks what this round funds.
Each layer depends on usage of the one before it, so the stack compounds as monitored cases, correspondence and agent calls accumulate.
Each step adds courts to the same model of cases, parties, events and documents. It is not a new product per jurisdiction.
All districts, live.
Same national case-number system, same feeds.
California, New York, Texas, Florida and Delaware.
Led by real unsupported-case demand from users.
The same graph, beyond the courtroom.
Capital is being used to accelerate a working system, not to discover whether a product can be built. Live court lookups, billing and the MCP endpoint were all in production within the first week.
A small team ships at the pace of a much larger one.
The free case check is the top of the funnel.
Public pages for search, MCP for assistants.
Sign up, check a case and start a trial with no call.
Stripe checkout, no sales cycle below enterprise.
Every court added feeds every product at once.
No large outbound sales organization is planned below enterprise contracts.
$3,000,000
The core platform, the Case Graph, enterprise controls and the intelligence layer.
Court ingestion, normalization and jurisdiction coverage.
Durable search, agent and product-led acquisition channels.
Deep integrations across AI assistants and agent ecosystems.
Enterprise trust, controls and compliance readiness.
Selective high-value customer acquisition and expansion.
Corporate operations and contingency.
Substantially expanded U.S. litigation coverage, starting with appellate and bankruptcy.
Millions of additional normalized events and the relationships between them.
Enterprise-grade deployment, controls and compliance readiness.
Deep, maintained integrations across the major assistants.
API and MCP usage priced for applications, not just people.
Agent-originated customer acquisition tracked end to end.
More professional and practice accounts with more matters each.
Insurers, litigation finance and compliance teams.
CaseMagic is the litigation data layer for AI. It monitors federal court cases, captures case correspondence, keeps one persistent structured record per matter (the Case Passport), and makes that record available to people and to AI assistants such as ChatGPT and Claude through an MCP endpoint.
A legal AI assistant reasons over what it is handed. CaseMagic is what it is handed: the persistent, continuously updated record of a case that any assistant can call. Assistants are distribution channels for CaseMagic, not competitors.
Federal dockets and filings come from CourtListener and its RECAP archive, and new cases come from the district courts’ own public filing feeds, read every five minutes. Private context comes from the user: correspondence sent to a case’s CaseMail address and documents they add.
It is the structured graph CaseMagic is building of matters, parties, counsel, judges, filings, deadlines, correspondence, companies and related cases. Today the Case Graph links courts, cases, docket events, documents, deadlines, correspondence and the companies and plaintiffs named across new federal suits; this round funds extending it into the full Litigation Knowledge Graph.
Not the public filings, which anyone can obtain. What is proprietary is the structure built on top of them: normalized events, persistent Case Passports, the private correspondence attached to each matter, the record of how agents use it, and the relationships derived across cases.
Yes. CaseMagic is available to ChatGPT as an app over MCP, and production has recorded real case lookups from ChatGPT’s own client. Claude, Grok and Muse connect the same way, and Gemini through function calling.
Because that is where people now ask about their cases. Every assistant that can call CaseMagic is a channel that brings users to the record, and every link an assistant prints is attributed back to it.
Monthly subscriptions per monitored matter: Individual $99, Professional $299 and Practice $599 per month, with a 7-day trial. Enterprise contracts and usage-based API pricing are the next layers.
CaseMagic shares revenue and customer figures with investors directly, in the investor deck.
Active U.S. federal civil litigants: self-represented litigants, small litigation practices and small firms with active federal matters.
One national case-number system across every district, public filing feeds and one consistent docket format. That makes it the fastest place to prove the data model before adding state courts.
Nothing stops anyone copying the software. What is hard to copy is a graph enriched continuously by monitored cases, private correspondence and agent usage, together with distribution already established inside the assistants. That position compounds with usage, which is why speed matters now.
Every case belongs to one organization and every request is answered only for the organization that owns it. An assistant reaches a private matter only after the user signs in to CaseMagic and authorizes it over OAuth. Pages behind a sign-in carry a no-index header, and payments are handled by Stripe. The security page sets out what is stored, who can reach it and what CaseMagic does not claim.
Product & Engineering 30%, Data Infrastructure 20%, Growth & Distribution 20%, AI-Agent Ecosystem 10%, Security & Compliance 7.5%, Sales & Customer Success 7.5%, Legal, Admin & Reserve 5%.
Use “Request Investor Deck” on this page. Only a name and an email address are required; the founder sends the deck personally.
CaseMagic is building the infrastructure layer that makes that possible.
Courts create litigation. CaseMagic structures it. AI agents consume it.