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 breakdown 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: risk score, grade, geography, 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, Pro and Scale plans add components and contributors so your team can explain what is driving the score.

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 is adding 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 score is a 0 to 100 modeled neighborhood risk score. Lower scores represent safer relative standing and higher scores represent higher modeled risk.

Does the API return a grade?

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

Do higher tiers return more detail?

Yes. Starter returns score and grade, Pro adds component breakdowns, and Scale adds contributing factors and higher-volume usage.