Why raw crime data is not enough
Most crime APIs start with incident rows. That can help if you are building a public blotter, but it puts a lot of cleanup work on your team. Categories vary by city, update timing is uneven, and population density can make busy places look worse without context.
CrimeScore is built for teams that need a product-ready signal. You send coordinates, we resolve the Census block group, and the API returns a neighborhood risk score with the response detail available on your plan.
What the API returns
The score endpoint returns a 0 to 100 risk score, a letter grade, resolved location metadata, and model data. Higher tiers add component breakdowns and top contributing factors.
The recent activity endpoint is separate. It gives bounded 24-hour local context without turning your app into a raw incident feed.
- Address and coordinate based scoring
- Census block group level resolution
- Overall, violent crime, property crime, and disorder components
- Embeddable crime map layers for customer-facing pages
Built for real product workflows
CrimeScore is useful when crime data is one part of a larger user decision, like comparing listings, reviewing markets, enriching location profiles, or giving customers a safer way to understand neighborhood context.
The API is not designed for predictive policing, individual screening, or any workflow that makes a legally adverse decision about a specific person based on their address.