Last updated: 23 September 2026
eCourtsIndia.com is a private, non-government platform that turns India’s public court records into one searchable index, and we built it in stages between April 2025 and today. We registered the domain in April 2025, the public search site was live by mid-2025, and by September 2026 the index held 32 crore+ case records across the Supreme Court, all 25 High Courts, district and taluka courts in all 36 states and union territories, and 18 tribunal and commission types. This is our build log, with dates you can check for yourself.
This is not an internal-metrics post. We do not share revenue, valuation or fundraising details here. We share what we built, roughly when it shipped, and what we learned doing it. Where we give a date, it comes from a public record: a domain registration, an Internet Archive snapshot, an app store listing, or a launch post on this blog. Where we could not pin a date down, we say so rather than guess.
Key takeaways
- 2025 was about getting the data to hold still: one schema across very different court portals, identity resolution, and a crawl that survives portal changes.
- 2026 turned a search site into a set of products: the AI Clerk, WhatsApp and email case alerts, tribunal coverage, IndiaCode, LegalCheck and the tribunal CNR generator.
- Case search, cause lists and the directories stay free. Paid credits cover work that costs us money to do, such as tracking, alerts, AI summaries and document downloads.
- Two early beliefs turned out wrong: that consumers mattered less than developers, and that we would stay pure infrastructure. The apps, alerts and AI Clerk are the correction.
- Everything is searchable at ecourtsindia.com/search, and developers can build on the API or the MCP server.
The build at a glance
The short version: domain in April 2025, public site by mid-2025, iOS app in December 2025, then a steady run of product launches from April 2026 onwards. The table lists each milestone with the public record that dates it.
| When | What shipped | How you can check the date |
|---|---|---|
| April 2025 | ecourtsindia.com domain registered | Public domain registration record (RDAP), 10 April 2025 |
| June 2025 | Public site online | Earliest Internet Archive snapshot of the home page, 16 June 2025 |
| December 2025 | eCourts India iOS app | Apple App Store listing, first released 1 December 2025 |
| April 2026 | This knowledgebase, the search guides and the MCP series for AI agents | Blog posts dated 16 to 24 April 2026, including MCP 101 for legal teams |
| May 2026 | Developer API guide and free advocate profile claims | API guide (18 May) and claim your advocate profile (23 May) |
| June 2026 | AI Clerk; NCLT, NCLAT, ITAT, CESTAT, SAT, DRT, DRAT, TDSAT, APTEL and consumer commissions | Meet the AI Clerk (2 June), NCLT and NCLAT launch (9 June) and the tribunal posts that followed |
| July 2026 | GSTAT, NGT, AFT, RCT, CAT, CCI, SEBI and GST AAAR orders; WhatsApp and email case alerts; MCP connector for Claude | GSTAT launch (10 July), case alerts guide and MCP connect guide (23 July) |
| August 2026 | IndiaCode: bare Acts, sections and the judgments that cite them | IndiaCode launch (24 August) |
| September 2026 | LegalCheck background checks and partner API; tribunal CNR generator | LegalCheck launch (14 September), LegalCheck API (15 September), tribunal CNR spec (22 September) |
Some things are live today but do not have a clean public launch date we can point to, so they are not in the table: the Chrome extension, the Android app, Crime Reports with 12 lakh+ FIR PDFs from 13 states and union territories, the verified advocate directory and Add a Missing Case.
2025: getting the data to hold still
The first stretch of work was unglamorous and mostly invisible. India publishes a huge amount of court data, but it publishes it through many portals built at different times by different teams. Before anyone could search it well, it had to be made consistent.
- Schema consistency across states. Each state and each High Court presents slightly different fields, orderings and conventions. Normalising all of it into one schema without losing local meaning was the hardest problem of the year. The same case type can be spelt three ways inside one court complex. Today we map 269 case type codes and 71 case status codes, and the Case Type Encyclopedia documents them.
- Entity resolution. The same company shows up as “ABC Pvt Ltd”, “ABC Private Limited” and “ABC (India) Pvt Ltd”. People show up in every spelling of their names. Clean entity resolution is what separates a database from a dataset, and it later became the foundation of LegalCheck.
- Crawl stability. Public portals change shape, rate-limit unpredictably and go offline for maintenance. Keeping a national index fresh across 36 states and union territories is a full-time infrastructure job, and we try to do it while respecting the portals’ limits.
- Freshness. “Daily” is not one thing. Some courts publish within hours of a hearing, others days later. Being honest about that lag matters as much as reducing it.
The CNR, the 16-character number every district and High Court case carries, turned out to be the spine that held all of this together. If you want to understand why, our CNR Number Decoded guide explains the format.
2026: from a search site to a set of products
By early 2026 the index was big enough to be useful and stable enough to build on. The rest of the year has been about putting products on top of it for different readers.
- For lawyers: the AI Clerk, a personal legal clerk that organises matters by client, keeps them in sync with the court record and reads orders. It runs on credits: 50 free credits a month, then plans from Rs 250 + GST a month. Advocates can also claim a free profile and get bar-card verified.
- For litigants: WhatsApp and email case alerts when a new order, hearing date or application lands, plus Android and iOS apps and a Chrome extension. Viewing a case stays free; a delivered alert costs Rs 0.50 and tracking costs Rs 5 per case per month.
- For specialist forums: a tribunal rollout that started with the company law benches and now covers 18 tribunal and commission types, with 44 lakh+ tribunal records. Tribunals do not issue CNRs the way courts do, so we built a tribunal CNR generator for 14 tribunals and published the spec.
- For statute research: IndiaCode, with 10,084 Acts and 2,69,602 provisions, each linked to the judgments that cite it. The IndiaCode launch post explains how it is built.
- For BGV, lending and KYB teams: LegalCheck, an identity-first background check, and its partner API.
- For developers and AI agents: the REST API with 23 endpoints and Rs 200 in free credits, and the MCP server, now at version 4.46 with 39 tools across cases, cause lists, the statute book and the electoral roll.
Five things that mattered more than we expected
- Identity, not keywords. A name search returns everyone with that name. Deciding which records belong to one person is a different, harder problem, and it is the one buyers actually care about.
- Honest coverage statements. Readers forgive a gap they were told about. They do not forgive a clean result that turns out to be incomplete. That is why we built Add a Missing Case, so anyone can tell us when a matter is not in the index.
- Tribunals. We underestimated how much of India’s commercially important litigation sits outside the court hierarchy, in the NCLT, DRTs, ITAT and consumer commissions.
- Content. People search for plain answers: what a CNR is, how to read a cause list, what a case status means. Writing those answers well mattered far more than we planned, and this knowledgebase exists because of it.
- Pricing clarity. Free search plus small, visible per-action charges is easier for a district court advocate to trust than a large subscription. The pricing page lists every charge.
What we got wrong, and changed
An earlier version of this post said consumer experience mattered less than developer access, and that we would stay focused on infrastructure rather than destination products. Both statements aged badly, so we are correcting them here rather than quietly deleting them.
- Consumers mattered more than we thought. Litigants wanted to know when their case moved, on the phone they already use. WhatsApp alerts, the apps and the Chrome extension came from that.
- We did build destination products. The AI Clerk and LegalCheck are products in their own right, not just data pipes. The data layer is still the foundation; it is just no longer the only thing we ship.
- Pricing became credit-based. Paid work now runs on credits that never expire, because usage varies wildly between a solo advocate and a firm.
Three decisions we would defend
- API-first. We documented the API early and kept it stable. It is how BGV platforms, lenders and legal AI startups plug in without scraping, and our scraping to production post explains why that matters.
- MCP early. We had an MCP server running by April 2026, when we published our MCP series. It put Indian court data inside Claude and other agent tools before most of the category had looked at Indian sources.
- Respectful positioning. We are a complement to the official eCourts system, Indian Kanoon and the rest of the ecosystem, not a replacement. The official record remains the authority, and our public data, private experience manifesto sets out what we commit to.
What we are still working on
- Deeper coverage of taluka courts, where data arrives more slowly.
- High Court and tribunal cause lists. Our cause-list dataset covers district and taluka courts today, with 7 crore+ entries, and we say so wherever it matters.
- Better search across regional-language orders.
- Judge-level analysis that respects how sensitive that kind of product is.
- FIR coverage beyond the 13 states and union territories in Crime Reports today.
What this means for eCourtsIndia
The foundation is laid: one national index of 32 crore+ case records and 125 crore+ orders and judgments, a lawyer directory of 34 lakh+ advocates and 82,000+ judges, and a set of products for lawyers, litigants, businesses and developers on top. We remain a complement to the public eCourts system, not a replacement for it. The next stretch is about depth: more courts, fresher data and fewer gaps, each one announced on this blog with a date you can check.
If you want the bigger picture of how these pieces fit, read the Operating System for Indian Law and the Zerodha playbook for Indian legaltech.
Search any case free at ecourtsindia.com/search, read the API documentation, or connect the MCP server to your AI stack.
Related reading
- The Zerodha Playbook for Indian Legaltech
- Why the data layer owners own the outcomes
- Mapping India’s Court Data Stack
- The eCourtsIndia Search Guide
Sources
- Domain registration record for ecourtsindia.com (RDAP), registration date 10 April 2025
- Internet Archive Wayback Machine, earliest capture of ecourtsindia.com, 16 June 2025
- Apple App Store listing for eCourts India (id6755883790), release date 1 December 2025
- Launch posts on blogs.ecourtsindia.com, April to September 2026, linked in the table above
- Index figures read from the eCourtsIndia MCP server, 23 September 2026
- eCourts Services Portal, ecourts.gov.in
Frequently Asked Questions
What is eCourtsIndia.com and what does it cover?
eCourtsIndia.com is a private, non-government platform that indexes India’s public court records. It covers 32 crore+ case records across the Supreme Court, all 25 High Courts, district and taluka courts in all 36 states and union territories, and 18 tribunal and commission types. Search, cause lists and directories are free at eCourtsIndia search.
When did eCourtsIndia launch?
The ecourtsindia.com domain was registered on 10 April 2025, and the earliest public snapshot of the site in the Internet Archive dates to June 2025. The iOS app followed in December 2025, and this knowledgebase started in April 2026. It opened with guides such as MCP 101 for legal teams, and every later launch has its own dated post.
What has eCourtsIndia launched in 2026?
In 2026 eCourtsIndia launched the AI Clerk, WhatsApp and email case alerts, coverage of 18 tribunal and commission types, the MCP connector for Claude, IndiaCode for bare Acts, LegalCheck background checks with a partner API, and a tribunal CNR generator. Each launch has a dated post on this blog, starting with Meet the AI Clerk.
Does eCourtsIndia replace the official eCourts portal?
No. eCourtsIndia is a complement to ecourts.gov.in and the wider ecosystem, not a replacement. The official court record remains the authority, and every record traces back to its originating court. eCourtsIndia adds one national search, alerts, AI summaries and developer access on top. You can check any case through eCourtsIndia and cross-check it on the official portal.
Can developers build on eCourtsIndia court data?
Yes. The REST API has 23 endpoints and new accounts get Rs 200 in free credits to test with real data. AI agents can connect to the MCP server, now at version 4.46 with 39 tools across cases, cause lists, the statute book and the electoral roll. Start with the eCourtsIndia API and its documentation.
How do I research a judge or advocate on eCourtsIndia?
Judge pages list a judge’s cases with bench, case-type filters and recent orders, and advocate pages show a counsel’s cases across courts. The directory covers 34 lakh+ advocates and 82,000+ judges, and advocates can claim and verify their profile for free. Open a judge page or find a lawyer directly.