Install Jentic One Beta

Connect the Common Platform API Case URN Mapper to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Common Platform API Case URN Mapper, 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%2Fswaggerhub.hmcts-dts%2Fcommon-platform-api-case-urn-mapper" | sh

Step 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%2Fcommon-platform-api-case-urn-mapper" | 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 Common Platform API Case URN Mapper API.

getCaseIdByCaseUrn

Manage maps geolocation data programmatically

Integrate Common Platform API Case URN Mapper into automated workflows

GET STARTED

Start building with Common Platform API Case URN Mapper API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Common Platform API Case URN Mapper API for, with concrete tasks.

★ Maps and Geolocation Operations

Use the Common Platform API Case URN Mapper to perform maps geolocation operations programmatically. The API provides 1 endpoints covering core functionality including getcaseidbycaseurn.

Call GET /urnmapper/{case_urn} to getcaseidbycaseurn

Data Retrieval and Monitoring

Query Common Platform API Case URN Mapper 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 Common Platform API Case URN Mapper endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call Common Platform API Case URN Mapper 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 'getcaseidbycaseurn', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — case url mapper specification.

METHOD

PATH

DESCRIPTION

GET

/urnmapper/{case_urn}

getCaseIdByCaseUrn

GET

/urnmapper/{case_urn}

getCaseIdByCaseUrn

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Common Platform Case URN Mapper by hand means coding its single lookup call against the service host and handling errors and retries yourself, even though it declares no auth scheme. Through Jentic you install once, import the Case URN Mapper from the API Directory, and your agent calls it.

Permission scoping

This API puts the case URN in the URL path (/urnmapper/{case_urn}), so a rule can pin your agent to that lookup: it can map a case URN to its case id and nothing else. This is the only operation exposed, and you choose whether the agent may call it.

Credential isolation

This Case URN Mapper 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 'get a case id by case URN', and Jentic returns the matching Case URN Mapper operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Common Platform API Case URN Mapper API through Jentic.

What authentication does the Common Platform API Case URN Mapper use?

The Common Platform API Case URN Mapper 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 getcaseidbycaseurn with the Common Platform API Case URN Mapper?

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

What are the rate limits for the Common Platform API Case URN Mapper?

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 getcaseidbycaseurn through Jentic?

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

How many endpoints does the Common Platform API Case URN Mapper have?

The Common Platform API Case URN Mapper exposes 1 endpoints covering caseidbycaseurn operations.

Can I limit what my agent is allowed to do with the Common Platform API Case URN Mapper?

Yes. Because Jentic One is self-hosted, you write the rules that decide which operations and credentials your agent may use. This API exposes a single operation that maps a case URN to its case id via the /urnmapper/{case_urn} path, so you can allow that one lookup and nothing else, or withhold it entirely.

Hmcts Dts Common Platform API Case URN Mapper

Name: Common Platform API Case URN Mapper API
Brand: Common Platform API Case URN Mapper
Availability: InStock

Browse all Swaggerhub Hmcts Dts APIs

Community OpenAPI document · agent-readyMaps GeolocationGeocodingnone1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically getcaseidbycaseurn. Covers 1 operations.

Use for: I need to getcaseidbycaseurn, Find available maps geolocation operations, Get the current status of Common Platform API Case URN Mapper resources, List all records from Common Platform API Case URN Mapper

Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.

Case URL Mapper specification. The API exposes 1 endpoints.

Jentic One on Github View OpenAPI Document

Connect the Common Platform API Case URN Mapper to your agent

Capabilities

Start building with Common Platform API Case URN Mapper API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hmcts Dts Common Platform API Case URN Mapper