Install Jentic One Beta

Connect the UK Police Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UK Police Data 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdata.police.uk%2Fdata-police" | 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%2Fdata.police.uk%2Fdata-police" | 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 UK Police Data API.

Retrieve street-level crimes within a custom boundary or around a single point for a given month

Follow the outcomes recorded for a specific crime by its persistent crime identifier

List every police force across England, Wales, and Northern Ireland and read a single force's details

Look up the neighbourhoods a force covers and the senior officers who lead it

GET STARTED

Start building with UK Police Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use UK Police Data API for, with concrete tasks.

★ Agent-Driven Local Crime Lookups

An AI agent answers questions about local safety by pulling street-level crime and stop-and-search records for an area from the UK Police Data API. The agent passes a point or a custom boundary, groups the returned crimes by category, and cites the last-updated date so the answer reflects the freshest monthly release. Because the data is open, the agent reads it directly with no credential to manage.

Fetch all street-level crimes within a boundary around a given latitude and longitude for the most recent month and summarise the counts by crime category

Force and Neighbourhood Directory

Build a directory of UK police forces and the neighbourhoods they police: list every force, read a single force's details and senior officers, then enumerate that force's neighbourhoods. This routes a resident of a given area to the right local policing team and its contacts.

List all police forces, then retrieve the neighbourhoods and senior officers for the force whose id is 'metropolitan'

Crime Outcome Tracking

Track what happened after a crime was reported by following its recorded outcomes. Given a crime's persistent identifier, the API returns the sequence of outcomes, letting a case-tracking tool show whether an investigation led to a charge, a caution, or no further action.

Retrieve the outcomes recorded for a crime using its crime identifier and report the latest outcome category

Stop-and-Search Transparency

Surface stop-and-search activity for public-transparency dashboards by pulling records at street level for an area or across a whole police force. Each record carries the context the force published, so analysts can compare activity between locations and forces over time.

Fetch stop-and-search records for a given police force for a specified month and count them by recorded outcome

Key Endpoints

12 endpoints — the uk police data api provides street-level crime, outcome, and stop-and-search records alongside details of police forces and neighbourhoods across england, wales, and northern ireland.

METHOD

PATH

DESCRIPTION

GET

/crimes-street/{crime_category}

Street-level crimes in an area for a month

GET

/crimes-at-location

Crimes recorded at a precise location

GET

/outcomes-for-crime/{crime_id}

Outcomes recorded for a specific crime

GET

/forces

List all police forces

GET

/forces/{force_id}/senior-officers

Senior officers of a force

GET

/{force_id}/neighbourhoods

Neighbourhoods a force covers

GET

/stops-street

Stop-and-search at street level in an area

GET

/crime-last-updated

Date the crime data was last updated

GET

/crimes-street/{crime_category}

Street-level crimes in an area for a month

GET

/crimes-at-location

Crimes recorded at a precise location

GET

/outcomes-for-crime/{crime_id}

Outcomes recorded for a specific crime

GET

/forces

List all police forces

GET

/forces/{force_id}/senior-officers

Senior officers of a force

GET

/{force_id}/neighbourhoods

Neighbourhoods a force covers

GET

/stops-street

Stop-and-search at street level in an area

GET

/crime-last-updated

Date the crime data was last updated

Why Jentic?

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

Setup

The UK Police Data API needs no sign-up and no key, but by hand you still wire its base host, its paging, and the month date parameter yourself. Through Jentic you install once, import it from the API Directory, and your agent calls it.

Permission scoping

Every endpoint is a read-only lookup over open data, so you choose exactly which queries your agent may call, such as street-level crimes or force details. The force id and neighbourhood id travel in the URL path, so a rule can bind the agent to specific path operations.

Credential isolation

The UK Police Data API requires no credential, so your agent holds nothing sensitive to reach it. For any credentialed API you add beside it, your own Jentic One instance keeps that secret encrypted and injects it at execution time, never in the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'crimes near a location' or 'list police forces', and Jentic returns the matching UK Police Data operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using UK Police Data API through Jentic.

What authentication does the UK Police Data API use?

The UK Police Data API is open: its OpenAPI spec declares no security scheme, so the data endpoints need no API key or token and you can call them straight away. When you connect it through Jentic alongside APIs that do need keys, those other secrets stay encrypted on your own Jentic One instance.

Can I get crime data for a specific area with the UK Police Data API?

Yes. The street-level crimes endpoint accepts either a single point or a custom boundary and returns the crimes recorded in that area for a given month, grouped under the values from the crime-categories list. You can also pull crimes recorded at a precise location and the stop-and-search records for an area.

What are the rate limits for the UK Police Data API?

The OpenAPI spec does not specify rate limits. Check the official documentation at https://data.police.uk/docs/ for current limits and fair-use guidance before running high-volume queries.

How do I pull UK crime data through Jentic?

Add the UK Police Data API from the Jentic API Directory, then have your agent search by intent such as 'crimes near a location' and call the matching operation. Because the data is open, there is no credential step. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the UK Police Data API?

Yes. Every operation is a read-only lookup, so you grant your agent only the queries it needs, such as street-level crimes and neighbourhood details, and leave out the rest. The force and neighbourhood ids sit in the URL path, so a rule can also pin the agent to specific path operations, and every call it makes is logged.

Is there a UK Police Data API MCP server?

You don't need an MCP server to give your agent the UK Police Data API. Jentic connects it directly from the API Directory: import it and your agent can query crime and policing data right away, without another server loading tool definitions into its context.

Data Police Uk UK Police Data API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchnone12 EndpointsREST

For Agents

Query UK street-level crime, outcome, and stop-and-search data by location, and look up police forces and the neighbourhoods they cover. Returns open data with no API key required.

Use for: Find all street-level crimes reported near a set of coordinates last month, I want to see the outcomes recorded for a particular crime, List all police forces in England and Wales, Get the neighbourhoods covered by a specific police force

Not supported: Does not handle crime reporting, emergency dispatch, or case management. Use for retrieving UK street-level crime, outcome, and policing data by area only.

The UK Police Data API provides street-level crime, outcome, and stop-and-search records alongside details of police forces and neighbourhoods across England, Wales, and Northern Ireland. You query crimes within a custom boundary or around a single point, follow the outcomes recorded against a specific crime, and list the forces and neighbourhoods that cover an area. The data is open and refreshed monthly, and a dedicated endpoint reports the date the crime dataset was last updated so you know how fresh a result is.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

17%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the UK Police Data API to your agent

Capabilities

Start building with UK Police Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Data Police Uk UK Police Data API

Jentic AI Readiness Score

UK Police Data API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness