U.S. neighborhood safety data

See what surrounds the property.

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 maps

Current release: 237,711 scored Census block groups · 33,611 ZIP code profiles · 3,144 county profiles · Coverage and sources

CrimeScore public mapNew York area · Overall Safety Score Open the map
CrimeScore public map showing neighborhood Safety Score variation across the New York area

Search an address, city, or ZIP

No account required. Addresses open the public map; ZIP codes and cities of 10,000+ residents open their profile pages.

A ZIP average can hide local differences.

ZIP 11367 combines 38 scored Census block groups. The selected area shows why a local result can differ from the broader ZIP estimate.

CrimeScore account Safety Map with Model Factors open for Block Group 360810779041 at Safety Score 88, Grade A
CrimeScore account Safety MapZIP 11367 · Model Factors for 360810779041 Open ZIP 11367
ZIP 11367 estimate 42/100 Grade C Queens County, New York
Selected block group 88/100 Grade A 360810779041

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.

Score components

Compare the same component across locations; different components are not directly comparable.

Violent crime
41/100
Property crime
44/100
Disorder
40/100
Frequency
41/100

Modeled Safety Scores are not official crime rates or guarantees.

How to interpret CrimeScore

Four ways to use CrimeScore.

Use CrimeScore as a public map, comparison report, API response, or embedded map.

CrimeScore public map showing U.S. Safety Score coverage with layer and geography controls

Search the public map.

Start with U.S. coverage, then search an address or ZIP and switch between score layers and local geographies.

Sample report · 10 public locationsOpen sample PDF
Ten-location CrimeScore report with published scores and a Safety Score map

Compare up to 10 locations.

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.

GET /v1/score?zip=11367Authenticated request
{
  "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.

GET /v1/score/details?zip=11367&component=overallAPI key · Starter+ or evaluation
{
  "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.

GET /v1/incidents/nearby?lat=40.7128&lng=-74.006&radius_m=5000&hours=24API key · Pro+ · coverage varies
{
  "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.

Choose the endpoint you need.

Get a score, request contributor details, or add separate recent-incident context. Access varies by endpoint.

CrimeScore-owned live preview ZIP 11367 · hosted, theme-aware map Production embeds use publishable keys and approved domains.

Put the map in your product.

Choose the geography, score layer, starting location, and theme. This preview is CrimeScore-owned. Production embeds use publishable keys and approved domains.

Plans

Pick the plan that fits the work.

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.

Starter

$199.99/month

500 API requests per month

For property research and early integrations that need scores, components, and contributor detail.

Pro

$699.99/month

2,500 API requests per month

For higher-volume integrations that need nearby incidents and unwatermarked embeds.

Enterprise

Custom

Volume and delivery agreed in the contract

Contract-led deployments that need volume, delivery, or terms beyond the self-serve plans.

ZIP variation study 67.2%

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 study

Method and limits

Know the score’s 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

Tell us what you’re evaluating.

Share your workflow and we’ll help you choose between account reports, REST API access, hosted maps, or a custom data discussion.

Discuss a data workflow

Tell us the closest use case and we’ll start there.

We use your details to respond to this request. See our Privacy Policy.