Crime Score API

A crime score API for address-level context.

A crime score should be easier to explain than a spreadsheet of incidents. CrimeScore turns location signals into a clear score, grade, and component scores that teams can use inside apps, dashboards, and map experiences.

crime score APIaddress crime score APIcrime risk scoreneighborhood risk scorecrime score by address

A score that fits into a product

The API response is intentionally simple at the surface: Safety Score, grade, geography, components, and model metadata. That makes it easier for product teams to show a clear signal without asking users to interpret raw crime tables.

When you need more detail, Starter adds score details for contributor explanations, while Pro and Enterprise add recent incident context and higher-volume options.

Local scores with broader lookup paths

ZIP codes are useful for broad search, reporting, and market pages. Address and coordinate-based workflows usually need a more local score too.

CrimeScore scores Census block groups for local context, supports county and state map layers for broader browsing, and supports ZIP-code lookups as a higher-level API surface.

Responsible boundaries

CrimeScore is a statistical location-risk signal. It is not a policing tool, a personal risk score, or a substitute for legal review.

Protected attributes are excluded from scoring, and prohibited uses are called out in our terms and methodology.

FAQ

Common questions

What does the score mean?

The Safety Score runs from 0 to 100. Higher scores represent safer relative standing, and A is the best grade.

Does the API return a grade?

Yes. The score endpoint returns a letter grade along with the numeric Safety Score.

Do higher tiers return more detail?

Yes. Starter includes score details with contributors, direction, and impact. Pro adds nearby incidents, and Enterprise adds custom volume and support.