Starter
$199.99/month
500 API requests per month
For property research and early integrations that need scores, components, and contributor detail.
U.S. neighborhood safety data
Modeled Safety Scores for U.S. neighborhoods, with the contributors behind each result. Delivered as account reports, a REST API, and embeddable maps your product can ship.
Reports, APIs, and embedded mapsCurrent release: 237,711 scored Census block groups · 33,611 ZIP code profiles · 3,144 county profiles · Coverage and sources
No account required. Addresses open the public map; ZIP codes and cities of 10,000+ residents open their profile pages.
Try a five-digit ZIP code, or browse the full map.
ZIP 11367 combines 38 scored Census block groups. The selected area shows why a local result can differ from the broader ZIP estimate.
46 points apart inside one ZIP. Scores run from 0 to 100, and higher is safer. A ZIP code estimate summarizes 38 scored local areas (Census block groups). That figure is a count, not a coverage percentage.
Compare the same component across locations; different components are not directly comparable.
Modeled Safety Scores are not official crime rates or guarantees.
Use CrimeScore as a public map, comparison report, API response, or embedded map.
Start with U.S. coverage, then search an address or ZIP and switch between score layers and local geographies.
Owners and admins with evaluation credits or an active API plan can compare one input type at a time and export PDF or CSV. Each successful location uses 10 credits.
New accounts start with 25 evaluation credits for 30 days, enough to try a 2-location report without a payment method.
Public locations with published CrimeScore data as of October 5, 2026. Scores describe the surrounding block group, not the individual property. No customer data is included. Different components are not directly comparable.
{
"zcta": "11367",
"resolved": {
"zip": "11367"
},
"safety_score": 42,
"safety_grade": "C",
"components": {
"violent_crime": 41,
"property_crime": 44,
"disorder": 40,
"frequency": 41
},
"data": {
"model_version": "2.0",
"block_group_count": 38
}
} Example populated from the current published ZIP release.
{
"zcta": "11367",
"resolved": {
"zip": "11367"
},
"component": "overall",
"safety_score": 42,
"safety_grade": "C",
"contributors": [
{
"label": "<strongest local factor>",
"direction": "lowers_safety_score",
"impact": "high"
},
{
"label": "<second local factor>",
"direction": "raises_safety_score",
"impact": "medium"
}
],
"data": {
"model_version": "2.0",
"block_group_count": 38
}
} Sanitized contributor example from the current ZIP release.
{
"capturedAt": "<ISO-8601 timestamp>",
"center": {
"lat": 40.7128,
"lng": -74.006
},
"radius_m": 5000,
"hours": 24,
"count": "<number>",
"incidents": [
{
"label": "<normalized incident label>",
"categories": [
"<category>"
],
"reportedAt": "<ISO-8601 timestamp>",
"distance_m": "<number>"
}
]
} Response shape only, not a live incident lookup.
Get a score, request contributor details, or add separate recent-incident context. Access varies by endpoint.
Choose the geography, score layer, starting location, and theme. This preview is CrimeScore-owned. Production embeds use publishable keys and approved domains.
Plans
Public maps and ZIP profiles stay free. New accounts can evaluate API calls and reports with 25 credits. Paid plans add recurring allowances and customer embeds.
$199.99/month
500 API requests per month
For property research and early integrations that need scores, components, and contributor detail.
$699.99/month
2,500 API requests per month
For higher-volume integrations that need nearby incidents and unwatermarked embeds.
Custom
Volume and delivery agreed in the contract
Contract-led deployments that need volume, delivery, or terms beyond the self-serve plans.
Public maps
Open a county map, then search the address or ZIP that matters.
Guides and research
Read how scores work, where they apply, and how teams use them.
View all insights
Featured explainer · 2 min read How CrimeScore Turns Raw Crime Data Into Neighborhood Safety Scores A plain-language guide to what CrimeScore measures, how scores should be interpreted, and their limitations. Read the guide Product guide · 5 min read How to Add a Neighborhood Safety Score to a Real Estate Platform A practical guide for adding neighborhood safety scores, crime map embeds, and recent activity context to property search products. Read the guide Property research guide · 5 min read Where ZIP Code Crime Data Fits in Property Search ZIP-code crime data is useful for broad search and market pages, but property-level products usually need a local score alongside it. Read the guide In more than two in three of the 28,551 ZIP code areas studied, the highest and lowest contributing block-group Safety Scores were at least 40 points apart.
Read the ZIP variation studyMethod and limits
CrimeScore publishes comparable neighborhood estimates on a 0 to 100 scale using public reported-crime records and broad public location context. Higher is safer.
Source records reflect reporting and enforcement practices. Government estimates can lag change, and some areas are unavailable. CrimeScore is context. It is not an official crime rate or police report, a causal explanation, an investment recommendation, or a guarantee.
Professional evaluation
Share your workflow and we’ll help you choose between account reports, REST API access, hosted maps, or a custom data discussion.
Tell us the closest use case and we’ll start there.