Hmcts Dts RAG Service API

Name: RAG Service API
Brand: RAG Service API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone6 Endpoints

Install Jentic One Beta

Connect the RAG Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RAG Service 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 RAG Service API.

Initiate upload process by submitting document metadata

Get status for given document reference

Generate response for user query synchronously

Check status of asynchronous request to provide summarised answer for user query

GET STARTED

Start building with RAG Service API

Explore with Jentic

View OpenAPI Document

For Agents

Programmatically initiate upload process by submitting document metadata, get status for given document reference. Covers 6 operations.

Use for: I need to initiate upload process by submitting document metadata, I want to status for given document reference, Search for document status, Find all generate response for user query synchronously

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

Use Cases

Patterns agents use RAG Service API for, with concrete tasks.

★ Developer Tools Operations

Use the RAG Service API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including initiate upload process by submitting document metadata, get status for given document reference, get document status.

Call POST /document-upload to initiate upload process by submitting document metadata

Automated Document information summarised asynchronously Management

Automate document information summarised asynchronously operations by combining multiple RAG Service API endpoints. Agents can get status for given document reference and then get document status in a single workflow.

Call GET /document-upload/{documentReference} to get status for given document reference, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RAG Service 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 'initiate upload process by submitting document metadata', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — api for rag service for document ingestion and answer retrieval.

METHOD

PATH

DESCRIPTION

POST

/document-upload

Initiate upload process by submitting document metadata

GET

/document-upload/{documentReference}

Get status for given document reference

GET

/document-status

Get document status

POST

/answer-user-query

Generate response for user query synchronously

POST

/answer-user-query-async

Generate response for user query asynchronously

GET

/answer-user-query-async-status/{transactionId}

Check status of asynchronous request to provide summarised answer for user query

POST

/document-upload

Initiate upload process by submitting document metadata

GET

/document-upload/{documentReference}

Get status for given document reference

GET

/document-status

Get document status

POST

/answer-user-query

Generate response for user query synchronously

POST

/answer-user-query-async

Generate response for user query asynchronously

Why Jentic?

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

Credential isolation

This RAG Service API declares no credential, so there is nothing to store. If your deployment later requires one, your own Jentic One instance stores it encrypted and injects it at execution time so it never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'answer a user query from documents' or 'check document upload status', and Jentic returns the matching RAG Service 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 RAG Service API through Jentic.

What authentication does the RAG Service API use?

The RAG Service 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 initiate upload process by submitting document metadata with the RAG Service API?

Yes. Use the POST /document-upload endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RAG Service 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 initiate upload process by submitting document metadata through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'initiate upload process by submitting document metadata'. Jentic returns the matching RAG Service API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RAG Service API have?

The RAG Service API exposes 6 endpoints covering document information summarised asynchronously, document information summarised synchronously, document ingestion initiation operations.