Hmcts Dts Piloting API

Name: Piloting API
Brand: Piloting API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone1 Endpoints

Install Jentic One Beta

Connect the Piloting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Piloting API, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 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 instance

Jentic 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.

Capabilities

What an agent can do with Piloting API.

getJudgeById

Manage developer tools data programmatically

Integrate Piloting API into automated workflows

Query and filter Piloting API records by parameters

GET STARTED

Start building with Piloting API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Piloting API for, with concrete tasks.

★ Developer Tools Operations

Use the Piloting API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including getjudgebyid.

Call GET /example/judges/{judge_id} to getjudgebyid

Data Retrieval and Monitoring

Query Piloting API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary Piloting API endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Piloting API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'getjudgebyid', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — a simple api for the experiments that will help shape the api strategy.

METHOD

PATH

DESCRIPTION

GET

/example/judges/{judge_id}

getJudgeById

GET

/example/judges/{judge_id}

getJudgeById

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Piloting API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a judge by id', and Jentic returns the matching Piloting API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Piloting API through Jentic.

What authentication does the Piloting API use?

The Piloting API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I getjudgebyid with the Piloting API?

Yes. Use the GET /example/judges/{judge_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Piloting API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I getjudgebyid through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getjudgebyid'. Jentic returns the matching Piloting API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Piloting API have?

The Piloting API exposes 1 endpoints covering judges operations.

Can I limit what my agent is allowed to do with the Piloting API?

Yes. Because you run Jentic One yourself, your own rules decide which Piloting API operations and credentials the agent may use. The only operation is GET /example/judges/{judge_id}, and since the judge id sits in the URL path, a rule can pin the agent to a single judge lookup so it reads that one record and nothing else. You choose the operations it may call, so only the read you approve is included unless you add more.