Developer platform

Advocate OS gives your software the same court data the app reads: eCourts cases, cause lists and orders, judgments and bare acts with paragraph numbers, limitation worked out in code, and reports that check a person or a company for litigation. You call a JSON API with a key. You pay in rupees, per call, and a failed or empty call costs nothing.

Everything here also works from an AI agent: every page is a Markdown file, and the API has a Model Context Protocol server, an OpenAPI document and a llms.txt.

#Who this is for

• Banks, NBFCs and lenders who check borrowers and guarantors for litigation before they lend. Start with the litigation check guide.
• Legal-tech teams who need cases, orders and cause lists inside their own product, without running a court scraper.
• Law firms with engineers, who want their matters, hearings and deadlines in their own dashboards. See the workspace API.
• Builders of AI tools who need answers that cite a judgment and a paragraph, not a guess. See RAG over judgments.

#Try it in five minutes

The sandbox is a made-up High Court. It is free, it needs no payment, and it never touches a real court. The quickstart takes you from sign-up to your first call.

curl https://adv.heliosynctech.com/api/v1/cases/SBXX010000012026 \
  -H "Authorization: Bearer $AOS_KEY"

#The six families

Family	What it does	Page
Court data	Find a case, read its status, list orders, read cause lists, work out court fee	Court data
Research and law	Search judgments, read them by paragraph, check citations, read bare acts, count limitation	Research and law
Reports	Order a litigation check or a due-diligence report as a PDF	Reports
Monitoring	Watch a case or a person and get a signed webhook when something changes	Monitoring
Intelligence	Read scanned records, translate, summarise an order, answer a research question, draft	Intelligence
Workspace	Read and add to your own firm's matters, hearings, deadlines and tasks	Workspace

#How a call works

• Base address: https://adv.heliosynctech.com/api/v1. Send and receive JSON.
• Key: send Authorization: Bearer aos_test_… or aos_live_…. See authentication.
• Price: each response carries AOS-Credits-Charged. One credit is ₹1 before GST. See pricing.
• Mistakes: every error has a code and a doc_url that says how to fix it. See errors.
• Dates: yyyy-MM-dd, in Indian Standard Time.

#Words you will meet

These are the terms advocates use. The API uses them as they are.

• CNR (Case Number Record): the 16-character id of a case in the eCourts system, such as DLHC010012342024. It is unique across India. In the sandbox it looks like SBXX010000012026.
• Cause list: the court's list of cases it will hear on a day, in the order it will hear them.
• Next date: the date the court has fixed for the case's next hearing.
• Order: what the judge recorded at a hearing or at the end of the case. An order has text and usually a PDF.
• Disposed: the case has ended. Pending: it has not.
• Vakalatnama: the document a client signs to let an advocate act for them. In the workspace API it is one of the documents on a matter.
• Matter: a client's case as the firm manages it, with hearings, deadlines, tasks and documents.

#What the API does not do

It does not give legal advice. Where AI is involved (the intelligence endpoints), the output is a proposal for an advocate to read and approve, and every answer points to the page or paragraph it came from. Deadlines, fees and prices are worked out by code with tests, not by AI.

Public court data is shared across firms. A firm's own data is never returned to another firm, and the workspace endpoints work only with that firm's own key.

#Next

1. Quickstart: your first call.
2. Sandbox: the test cases and what each one does.
3. Errors: what every error means.
4. Pricing: what a call costs.