Crime API providing information on Common Platform Prosecutor Interface (CPPI). The API exposes 4 endpoints secured with bearer authentication.
4 endpointsVersioned **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.
12 endpointsAPI for managing client subscriptions as standalone resources. The API exposes 7 endpoints secured with bearer authentication.
7 endpointsCase URL Mapper specification. The API exposes 1 endpoints.
1 endpointsAPI to retrieve court hearing case data, including defendants, offences, and results. The API exposes 1 endpoints.
1 endpointsAPI for court list publishing service. The API exposes 6 endpoints.
6 endpointsReference Data API providing information on Court Houses associated with a Court Hearing. The API exposes 2 endpoints.
2 endpointsReference Data API providing information on Judges associated with a Court Hearing. The API exposes 1 endpoints.
1 endpointsScheduling and Listing API providing the court schedule. The API exposes 1 endpoints.
1 endpointsScheduling and Listing API providing the court schedule. The API exposes 2 endpoints.
2 endpointsDCS Case Administration API Specification. The API exposes 4 endpoints secured with bearer authentication.
4 endpointsHMCTS Common Platform case administration status tracking APIs. The API exposes 2 endpoints secured with bearer authentication.
2 endpointsA simple API for the experiments that will help shape the API strategy. The API exposes 1 endpoints.
1 endpointsAPI for RAG service for document ingestion and answer retrieval. The API exposes 6 endpoints.
6 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.