Crime API providing information on Common Platform Prosecutor Interface (CPPI). The API exposes 4 endpoints secured with bearer authentication.
Versioned **queries** (user text + normalized prompt + lifecycle status) and **answers** linked to a Case. Clients can fetch: - The latest snapshot for a Case - An **as-of** view at a timestamp for reproducibility - A specific **version** of an answer. The API exposes 12 endpoints.
API for managing client subscriptions as standalone resources. The API exposes 7 endpoints secured with bearer authentication.
Case URL Mapper specification. The API exposes 1 endpoints.
API to retrieve court hearing case data, including defendants, offences, and results. The API exposes 1 endpoints.
API for court list publishing service. The API exposes 6 endpoints.
Reference Data API providing information on Court Houses associated with a Court Hearing. The API exposes 2 endpoints.
Reference Data API providing information on Judges associated with a Court Hearing. The API exposes 1 endpoints.
Scheduling and Listing API providing the court schedule. The API exposes 1 endpoints.
Scheduling and Listing API providing the court schedule. The API exposes 2 endpoints.
DCS Case Administration API Specification. The API exposes 4 endpoints secured with bearer authentication.
HMCTS Common Platform case administration status tracking APIs. The API exposes 2 endpoints secured with bearer authentication.
A simple API for the experiments that will help shape the API strategy. The API exposes 1 endpoints.
API for RAG service for document ingestion and answer retrieval. The API exposes 6 endpoints.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
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%2Fswaggerhub.hmcts-dts" | 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%2Fswaggerhub.hmcts-dts" | 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.