,

From Case Lookup to Case Intelligence: What Comes After the Government Portal

Case status lookup answers one CNR at a time. Case intelligence tracks every matter tied to a client or company. Five ways it works today, with costs.

From case lookup to case intelligence in India, cover design variant B for the eCourtsIndia blog

Features checked October 2026; prices checked November 2026. eCourtsIndia (ecourtsindia.com) is an independent, non-government platform, not affiliated with the eCourts project or any court.

A case status lookup answers one question about one matter: what happened on the last date, and when is the next one? Case intelligence answers a different question: what is happening across every case that affects this client, this company or this kind of dispute? The government eCourts portal is built for the first, and does it well: you type a CNR, solve a captcha and read a status page. Our guide on how to check court case status online covers that route.

This post is about the second question. It shows five ways case intelligence works on eCourtsIndia today, across 30 crore+ case records from the Supreme Court, all 25 High Courts, district and taluka courts and 18 tribunal and commission types, what each costs, and where the limits are.

Key takeaways

  • Case lookup is one CNR at a time. Case intelligence works across a portfolio, an entity or a whole category of cases.
  • Five practical uses: portfolio monitoring, counterparty checks, judge case history, cause-list checks and sector analysis.
  • Each maps to a live eCourtsIndia feature, from free search and cause lists to case tracking at ₹5 per case every 30 days (November 2026).
  • Case intelligence is not legal research: it watches live matters continuously instead of finding precedent occasionally.
  • Limits matter: court data can lag, a name match is not an identity match, High Court cause lists are not covered, and tribunal tracking is not available at present.

What does a case status lookup tell you, and what does it miss?

Case lookup is the basic transaction. The user knows one matter, identifies it by CNR or case number, and asks for the current status. The answer is hearing dates, parties, advocates, the last order and the next listing. The transaction is complete in a single response.

Case lookup answers a specific kind of question. Is my matter listed tomorrow? Has an order been uploaded? Who is the opposing counsel? What is the next hearing date?

Case lookup does not answer the questions that decide value at portfolio scale:

  • What is the full litigation exposure of this company across India?
  • Which advocates have appeared against this opposing counsel before, in which courts, and with what outcomes?
  • How has a particular bench of the Allahabad High Court at Lucknow handled cheque bounce matters?
  • Which of my 200 active matters are listed in the next seven days?
  • When did anyone last file a writ petition naming this state department, and what happened?
  • Are there parallel proceedings against the same party in two different courts, possibly argued by different lawyers in unrelated firms?
  • How long do partition suits take in Patna compared with Pune?

These are case intelligence questions. They need search across courts, matching of names across spelling variations, and history. A one-case lookup cannot deliver them, by design.

Why was the eCourts portal not built for this?

The eCourts Services portal, run under the e-Committee of the Supreme Court with NIC, is the right design for what it is. A public records system needs to answer one case at a time, behind a captcha to prevent bulk extraction, on infrastructure sized for millions of small queries. The architecture optimises for predictable cost per query and resistance to abuse. Our explainer on what the eCourts system is has the background.

That architecture does not fit intelligence at scale. Intelligence needs bulk access, structured outputs, entity resolution across spelling variations, and programmatic access with predictable contracts. Each of those is a different design choice from the one a public records portal makes.

We set out the wider architecture in The Operating System for Indian Law. The public portal is the foundation. The intelligence layer is built on top, by private actors who can invest in the structured aggregation work the public layer was not built to do. The relationship is complementary. The public substrate stays cheap and abuse resistant. The intelligence layer sits on top and serves the use cases the portal cannot.

Case lookup versus case intelligence compared: the question, the scale, the architecture, the buyer and the cadence

Five things case intelligence lets you do today

The product class is broad. Here are five concrete shapes, each with the part of eCourtsIndia that already does it.

1. How do I monitor all my matters in one place?

A General Counsel, a senior partner or an in-house legal operations lead wants one view of every active matter against the company or for a client, with next hearing dates, recent orders and advocates. The old answer was a Friday spreadsheet updated by a junior. On eCourtsIndia you add cases to a client file, from search or by CNR, or import them in bulk from the eCourts Services app. The AI Clerk then watches each tracked case on the official record, sends a WhatsApp or email alert when a date moves or a new order lands, and can read the order for you. At the time of writing (November 2026), tracking costs ₹5 per case every 30 days, each alert ₹0.50 per channel it is delivered on, and an AI read of an order ₹2. Tracking for tribunal and consumer commission matters is not available at present, though you can still search them and read their records. The setup is shown step by step in How to Enable Case Alerts for Any Court Case in India, and the lawyer’s version is in how to track all your pending cases in one place. Teams that prefer to work inside Claude can run the same check as a prompt, as described in Litigation Portfolio Monitoring for General Counsel.

2. How do I check a counterparty’s litigation exposure?

A bank, an insurer, a fintech or a background verification firm wants the litigation exposure of a borrower, applicant, vendor or counterparty, across all of India and every type of matter. Start with the free route: find all cases against a company by its name and spelling variants. For a person, the main risk is a namesake, which is why LegalCheck matches identity first and reports confirmed, probable and possible matches rather than every same-name hit. On the web a check costs ₹100 plus metered AI usage, with the first three completed checks free; through the partner API it is ₹99, or ₹33 with an active subscription (November 2026). We explained the method in the LegalCheck launch post, and the dataset idea behind it in Why India Needs a CIBIL for Litigation. For firms building their own screening flows, the eCourtsIndia API has 32 documented endpoints and ₹200 of free credits on signup, and this guide walks through a due diligence engine built on it.

3. Can I research a judge before a hearing?

You can see the judge’s matters. An advocate preparing for a hearing wants to see how the court has handled similar matters and read its recent orders; that knowledge used to live in the memory of senior partners. Judge pages at ecourtsindia.com/judge list the cases a judge has presided over, with the same filters as search (case type, status, dates) and links to the orders, and search itself can be filtered by judge name. How to Research Judge Profiles and Court Patterns shows the workflow. There are no judge scores or outcome predictions: the value is in reading the actual orders in matters like yours.

4. How do I check tomorrow’s listings across many courts?

A firm with two hundred active matters across forty courts wants tomorrow’s listings checked overnight, sorted by courtroom and item number. We described the pattern in The 5 AM Cause List Problem. Daily cause lists for district and taluka courts are free on ecourtsindia.com/causelist; High Court cause lists are not covered. The free eCourtsIndia Chrome extension shows tomorrow’s listings and case updates for the cases you follow, and the MCP server lets an assistant such as Claude run the whole check in one request.

5. What is happening across a whole category of cases?

A regulator, a journalist, a policy researcher or an academic wants to see what is happening across a category: PMLA, Section 138, family disputes, insolvency, election petitions. The data stories on this blog are examples, including the Bank Litigation Index, PMLA Bail After Vijay Madanlal Choudhary, The Election Petition Graveyard, Cheque Bounce at Scale and The Indian Disposal-Time Index 2026. Each one is built from filters and facets that anyone can re-run through the search, the API or the MCP server.

UseQuestion it answersLive on eCourtsIndiaCost at the time of writing (November 2026)
Portfolio monitoringWhat changed across my matters?Client files, AI Clerk tracking, WhatsApp and email alerts₹5 per case every 30 days, ₹0.50 per alert per channel delivered, ₹2 per AI order read
Counterparty checksWhat is this person’s or company’s litigation exposure?Litigant search, LegalCheck, APISearch free; LegalCheck on the web ₹100 + metered AI (first 3 checks free); partner API ₹99, or ₹33 with a subscription
Judge case historyWhat has this judge’s court done in matters like mine?Judge pages, judge filter in searchFree
Cause-list checksWhat is listed tomorrow in district and taluka courts?Free cause lists, Chrome extension, MCP serverFree cause lists; API and MCP usage billed on credits
Sector analysisWhat is happening across a category?Search facets, API, MCP server, published data storiesSearch free; API starts with ₹200 free credits
Five uses of case intelligence and the eCourtsIndia feature behind each, checked October 2026; prices checked November 2026. Current prices at ecourtsindia.com/pricing.

How is case intelligence different from legal research?

It is worth separating case intelligence from legal research, because the established Indian legaltech category, led by databases such as Manupatra and SCC Online, sits in the research lane.

Legal research is about precedent. You read judgments, build arguments around them and file briefs that cite them. The user is preparing for a hearing or writing a memo. The product is a search tool over a curated database of mostly appellate decisions.

Case intelligence is about ongoing matters and the entities behind them. You watch a portfolio, spot risk and measure patterns over time. The product is an alerting and reporting layer over a live, structured dataset of active and disposed matters.

These are different jobs. Research can largely ignore the district court tier because precedent value there is limited. Intelligence cannot, because that is where most of the activity is: the large majority of the 30 crore+ records on eCourtsIndia are district and taluka court cases. Research is opened occasionally. Intelligence runs in the background and tells you what changed.

The implication is that research databases and intelligence platforms will be judged as separate categories. Both can be valuable. They serve different jobs, different users and different budgets.

Why the intelligence layer is the bigger category

The buyer pool is wider than research’s: lawyers, in-house counsel, banks, insurers, background verification firms and corporate diligence teams all need to track or assess litigation exposure. The use is continuous rather than occasional. And the data gets better with use: tribunals are a recent example, with 18 tribunal and commission types now in the same search as the courts.

We made the wider market argument in India’s Legal AI Will Be a Ten Billion Dollar Category. The split between research and intelligence is part of that argument: intelligence is the half of the market that recurs.

What this means for product design

First, the product has to support portfolio thinking: not one CNR at a time, but a list, a client, an entity or a sector, with filters, client files and update alerts.

Second, the data has to be live. A weekly refresh is too slow; daily at minimum, and faster for the next day’s cause lists. On eCourtsIndia any case can also be refreshed from the official court server on demand, which matters because court records can lag.

Third, the data has to be reachable by AI assistants. Many users will not learn a new interface. They will ask in plain language through Claude, ChatGPT or a similar assistant, so the data has to be reachable through an MCP server that the assistant can call without the user leaving her chat tool. The eCourtsIndia MCP server does this (setup at ecourtsindia.com/api/mcp), and The AI Agent Layer for Indian Law sets out the architecture. Developers can start with our complete guide to the eCourtsIndia API.

What this means for eCourtsIndia

The portal does one-case lookup well. The work that remains is case intelligence at portfolio scale: lawyers monitoring two hundred matters at once, General Counsel running weekly risk briefs, banks checking counterparty litigation exposure, researchers watching sector patterns. Most of the five uses above already work on eCourtsIndia today.

If you want to try it on your own matters, search is free, the Android and iOS apps put tracking on your phone, and the Chrome Extension adds ₹100 of free credit a month at the time of writing. If a case you need is not in the index yet, use Add a Missing Case.

What to watch out for

  • Data lags. eCourtsIndia mirrors official court records, and a court may upload an order late. Before a hearing, refresh the case or check the court’s own record.
  • Names are not identities. A name search finds namesakes. Treat any hit on a person as unconfirmed until the parties, address or father’s name match.
  • Coverage gaps. High Court cause lists are not covered, and tracking for tribunal and consumer commission matters is not available at present.

Sources

Read next: The Operating System for Indian Law and Why India Needs a CIBIL for Litigation.

Frequently Asked Questions

How can I track many court cases at once in India?

Add each case to a client file on eCourtsIndia, by CNR or from search, and switch on WhatsApp or email alerts; cases saved in the eCourts Services app can be imported in bulk. The AI Clerk then watches every tracked matter and alerts you when a date moves or an order is uploaded. Tracking costs ₹5 per case every 30 days at the time of writing (November 2026).

What is the difference between case status and case intelligence?

Case status is one matter at a time: you enter a CNR and read the next date, parties and last order. Case intelligence looks across every matter tied to a client, company or category, so you can see total exposure, upcoming listings across courts and patterns over time. The first is what the eCourts portal does; the second needs aggregated data.

How do I check a company’s litigation exposure in India?

Search the company’s name and its spelling variants on the free eCourtsIndia case or litigant search, or run a LegalCheck, which matches a person or company to their court records with an identity-match level and a risk band. On the web it costs ₹100 plus metered AI usage, with the first three completed checks free, at the time of writing (November 2026).

Why can’t I bulk-download cases from the eCourts portal?

The government eCourts Services portal is built to answer one case at a time and uses a captcha to stop automated bulk extraction, which keeps it cheap and stable for millions of users. Portfolio-scale work needs structured, programmatic access, which independent platforms such as eCourtsIndia provide through an API and an MCP server.

Can I see how a judge has handled cases like mine?

You can see the judge’s cases. eCourtsIndia judge pages list the matters a judge has presided over, filterable by case type, status and dates, with links to the orders. They do not score judges or predict outcomes; reading the actual orders in similar matters is the useful part of the exercise.

Can Claude or ChatGPT read my court cases?

Yes, through the eCourtsIndia MCP server. You connect it once from Claude or ChatGPT and sign in with an eCourtsIndia account, and the assistant can then search cases, read orders and check district court cause lists on your behalf, with usage drawn from your credits. Setup instructions are on the MCP page at ecourtsindia.com/api/mcp.

eCourtsIndia is a private legal-technology platform. It is not affiliated with, associated with, or endorsed by the Government of India, the Supreme Court of India or its e-Committee, or any court. Official case information is published on ecourts.gov.in. Always verify details against official court records or certified copies. This article is general information, not legal advice. Spotted an error? Write to support@ecourtsindia.com.

Search 35 crore+ Indian court case records, free

One search across the Supreme Court, all 25 High Courts, district courts and 18 tribunal and commission types. Hearing alerts, AI summaries and an API for developers.