Neighborhood Safety Score API
People often search by ZIP code, then compare specific locations. CrimeScore gives product teams a neighborhood safety score that can be shown as a score, grade, component breakdown, or map layer.
A raw feed can overwhelm users. A safety score gives them a quick read, while components and maps let them dig deeper when they want to understand the area.
That matters for property search, relocation, portfolio review, and location intelligence products where safety is one factor in a bigger decision.
CrimeScore separates the long-term neighborhood risk score from recent incident activity. That keeps the score stable while still giving teams a current local pulse when their workflow needs it.
Neighborhood safety data can be sensitive. CrimeScore is designed for context and analysis, not individual screening, law-enforcement targeting, or decisions prohibited by fair-housing and civil-rights law.
FAQ
Yes. You can query a coordinate for an address and receive the score for the containing Census block group.
Yes, for permitted location-context use cases. Teams should present it as one signal among others and follow applicable law.
The long-term risk score is a modeled score. Recent activity is available through a separate bounded endpoint.