canonical: https://jentic.com/apis/data.police.uk/data-police # Data Police Uk UK Police Data API 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. ## For AI 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. ## Scope Does not handle crime reporting, emergency dispatch, or case management. Use for retrieving UK street-level crime, outcome, and policing data by area only. ## Capabilities - 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 - Fetch stop-and-search records by street location or by police force - Read the crime-categories reference list and the date the crime data was last updated ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Fetch stop-and-search records for a given police force for a specified month and count them by recorded outcome ## Key endpoints | 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 | ## Key resources - **Crimes** — Street-level crimes by area or point, crimes at a precise location, and the crime-categories reference list - **Outcomes** — Outcomes recorded against a specific crime identifier over time - **Forces** — All police forces, individual force details, and their senior officers - **Neighbourhoods** — The neighbourhoods a force covers, listed per force - **Stop and Search** — Stop-and-search records by street location or by police force ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 63 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 58 / 100 - AI-Readiness & Agent Experience: 42 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 55 / 100 - **View full report:** https://jentic.com/apis/data.police.uk/data-police/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **OpenCage Geocoding API** — Turns addresses into coordinates that the UK Police Data API needs for its location queries. - **positionstack** — Forward and reverse geocoding to resolve a point before querying crime data by location. - **Opendatasoft** — A general open-data platform hosting public datasets beyond UK policing. - **Data.gov** — US government open data for comparisons outside UK policing data. ## FAQ ### 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.