Get crimes nearby with a bounded incident API.

Search incidents near a coordinate

The nearby incidents route is designed for apps that already know a latitude and longitude, such as a map click, address lookup, listing page, delivery route, or location search.

Developers can request recent context by coordinate, radius, time window, and result limit, then show it beside the CrimeScore risk score and map layer.

• Coordinate-based lookup
• Radius and result limits
• Recent local context
• Sanitized incident categories

Product context, not a raw incident dump

The endpoint is intentionally bounded. It is not a bulk resale feed, dispatch system, emergency alert product, or replacement for official public safety records.

CrimeScore returns practical incident context for product workflows while omitting raw payloads, media, user data, and source identifiers.

Use it beside the score API

A long-term neighborhood score and a short-term nearby incident pulse answer different questions. The score explains modeled baseline risk. Nearby incidents explain recent activity around the selected place.

Keeping those signals separate makes the product easier to explain and keeps a single recent event from being treated like a full neighborhood risk model.

Example request

Use GET /v1/incidents/nearby?lat=40.7128&lng=-74.0060&radius_m=5000&hours=24&limit=25 for a bounded recent-activity lookup around a point.

Live requests require an API key. Public marketing pages show examples and route developers into the playground for authenticated testing.

{
  "lat": 40.7128,
  "lng": -74.006,
  "radius_m": 5000,
  "hours": 24,
  "count": 3,
  "candidate_count": 18,
  "truncated": false,
  "incidents": [
    {
      "category": "property",
      "label": "Theft",
      "occurred_at": "2026-06-23T13:42:00Z",
      "distance_m": 384,
      "source": "normalized_public_record"
    },
    {
      "category": "disorder",
      "label": "Disturbance",
      "occurred_at": "2026-06-23T09:10:00Z",
      "distance_m": 1280,
      "source": "normalized_public_record"
    }
  ]
}