Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AIRonline, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faironline.in%2Faironline" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faironline.in%2Faironline" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with AIRonline API.
Look up reported case citations by journal name, year, volume, and page number
Retrieve the full citation list for a court or publication segment
Browse Indian acts and the section lists contained within them
Fetch the judgement text for a specific reported case
Search the nominal index to find cases by court name
GET STARTED
Pull a case digest to review a judgement's holdings quickly
Patterns agents use AIRonline API for, with concrete tasks.
★ AI Legal Research Assistant
An AI agent connected to AIRonline through Jentic can answer legal research questions by resolving a citation reference into the reported case, pulling the judgement text, and summarising the holdings from the digest. The agent filters by journal, court, and year to find the right authority, then returns the citation list and judgement for review.
Look up the citation list for the Supreme Court in a given journal year, then fetch the judgement text for the first matching case
Citation Verification
Verify a legal citation by resolving its journal name, volume number, and page number against AIRonline's reported case records. The citation lookup confirms the court and case the reference points to, so a brief or memo cites the correct authority.
Resolve a citation given its journal name, volume number, and page number and confirm the court name it belongs to
Statute and Section Lookup
Retrieve Indian acts and the section lists within them so an agent can quote the correct statutory provision alongside case law. AIRonline returns the act list and the sections under a chosen act for statutory research.
List the acts available, then retrieve the section list for a chosen act
Case Digest Review
Pull a case digest to review a judgement's key holdings without reading the full text first. The digest view gives a condensed account of a reported case, letting an agent triage which judgements are worth retrieving in full.
Retrieve the digest for a reported case and extract its key holdings
15 endpoints — the aironline api retrieves indian reported case law, letting you look up case citations by journal name, year, volume, page, and court.
METHOD
PATH
DESCRIPTION
/aironline/api/citation/citationList
Retrieve a list of case citations
/aironline/api/citation/journalName
List available journal names
/aironline/api/citation/courtName
List court names for citation filtering
/aironline/act/act_list
List Indian acts
/aironline/act/section_list
List sections under an act
/aironline/api/judgement
Retrieve judgement text for a case
/aironline/api/citation/citationList
Retrieve a list of case citations
/aironline/api/citation/journalName
List available journal names
/aironline/api/citation/courtName
List court names for citation filtering
/aironline/act/act_list
List Indian acts
/aironline/act/section_list
List sections under an act
/aironline/api/judgement
Retrieve judgement text for a case
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AIRonline by hand means handling its bearer token auth and learning its citation, act, and judgement endpoints yourself. Through Jentic you install once, import AIRonline from the API Directory, store the token once, and your agent calls it.
Permission scoping
AIRonline exposes read operations across citations, acts, and judgements. You choose which operations your agent may call, so a rule can allow citation and act lookups while leaving the judgement retrieval out unless you add it.
Credential isolation
Your AIRonline bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up a case citation' or 'find a judgement', and Jentic returns the matching AIRonline operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using AIRonline API through Jentic.
Is there an AIRonline MCP server?
You don't need an MCP server to give your agent the AIRonline API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent can look up citations, acts, and judgements. Operations are discovered on demand, so your agent's context stays lean.
Can I limit what my agent is allowed to do with the AIRonline API?
Yes. Write a rule that allows only the citation and act lookup operations, so your agent can search reported cases and browse statutes but cannot pull full judgement text unless you add that operation, and every call it makes is logged.
What authentication does the AIRonline API use?
The AIRonline API authenticates with a bearer token per its OpenAPI spec, sent in the Authorization header. The judgement endpoint requires the token, while several citation lookups accept requests without it. With Jentic, the token is stored encrypted by your own Jentic One instance and injected at call time.
Can I look up a case by its citation with the AIRonline API?
Yes. The citation endpoints let your agent filter reported cases by journal name, year, volume number, page number, and court name, and return a citation list. From there your agent can fetch the matching judgement text or a digest of its holdings.
What are the rate limits for the AIRonline API?
The OpenAPI spec does not specify rate limits. Check the AIRonline website at https://www.aironline.in for current limits before running high-volume citation lookups.
How do I look up a case citation with the AIRonline API through Jentic?
Import the AIRonline API from the Jentic API Directory, store your bearer token once, and have your agent search by intent such as 'look up a case citation'. Jentic returns the citation lookup operation with its input schema, and your agent passes the journal and court filters. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Know of an official OpenAPI document? Contribute it →
For Agents
Look up Indian reported case citations, acts and their sections, judgement text, and case digests. Filter cases by journal name, year, volume, page, and court name.
Use for: Find all citations reported in a specific journal volume, Look up the judgement text for a reported case, Search for cases by court name in the nominal index, List the sections contained under a particular act
Not supported: Does not handle case filing, e-filing, or legal document drafting. Use for Indian case law citation lookup only.
The AIRonline API retrieves Indian reported case law, letting you look up case citations by journal name, year, volume, page, and court. It returns citation lists, full judgement text, and case digests, and it exposes acts with their section lists for statutory research. A nominal index lets you find cases by court name, making it a focused source for Indian legal citation lookups.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>