Address Geocoding API

Resolve US addresses before you score or map them.

The CrimeScore geocode helper turns a user-entered US address into normalized coordinates and Census geography. It is built for public search boxes, map centering, and product flows that need a clean address-to-location step before calling a paid scoring endpoint.

address geocoding APIaddress to coordinates APIUS address geocode APIcrime data by address APIcrime score by address API

API routes

What developers can call

Geocode GET /v1/geocode

Address to coordinates

Resolve a US address into latitude, longitude, matched address text, and optional Census geography. This helper is public and does not return a crime score.

GET /v1/geocode?address=1600%20Pennsylvania%20Ave%20NW%20Washington%20DC

{
  "query": "1600 Pennsylvania Ave NW Washington DC",
  "matched": true,
  "lat": 38.8977,
  "lng": -77.0365,
  "matchedAddress": "1600 PENNSYLVANIA AVE NW, WASHINGTON, DC, 20500",
  "state": "DC",
  "county_fips": "11001",
  "tract": "11001006202",
  "block_group": "110010062021"
}
Score GET /v1/score

Score the resolved coordinate

After geocoding, call the authenticated score endpoint with latitude and longitude to get the Safety Score, grade, resolved geography, components, and model metadata.

GET /v1/score?lat=38.8977&lng=-77.0365

{
  "geoid": "110010062021",
  "resolved": {
    "lat": 38.8977,
    "lng": -77.0365,
    "state": "DC",
    "county_fips": "11001"
  },
  "safety_score": 42,
  "safety_grade": "C",
  "data": {
    "census_vintage": "2024",
    "model_version": "2.0"
  }
}

Why geocoding is separate from scoring

Address search and crime scoring are different jobs. Geocoding resolves a typed address into a location. Scoring takes a known location and returns modeled neighborhood risk context.

Keeping those steps separate makes the API easier to reason about and prevents the public finder from exposing a secret score API key in the browser.

What the helper returns

The geocode helper returns only the normalized fields needed to center a map or prepare the next API call. It does not return raw Census payloads, a Safety Score, or paid tier details.

When the Census Geocoder can resolve geography, the response may include state, county FIPS, tract, and block group fields. Product teams can use those fields for display, logging, or debugging their location workflow.

  • Normalized matched address
  • Latitude and longitude
  • Optional Census geography
  • No score data
  • No customer quota usage

Best fit for public search

Use the public helper for simple US address search on map pages, onboarding flows, or demo experiences. It is intentionally not a polished autocomplete product like Google Places or Mapbox.

For production apps that already have coordinates from a listing database, mobile device, or internal geocoder, call the score API directly with latitude and longitude.

Responsible location context

CrimeScore uses address geocoding to help users understand location context. The result should not be treated as a guarantee about an address, a person, or a future event.

The score API remains the source of modeled neighborhood risk. The geocode helper is only the location-resolution step.

FAQ

Common questions

Does the geocode endpoint require an API key?

No. GET /v1/geocode is a public helper route used for address search and map centering. It does not return score data or consume customer quota.

Can I get a crime score from the geocode endpoint?

No. The geocode endpoint resolves a US address to coordinates. Use the authenticated score endpoint with the resolved latitude and longitude to get a CrimeScore Safety Score.

What happens if an address cannot be matched?

The API returns a NO_MATCH response when the address cannot be resolved. Users should enter a more complete street, city, and state when possible.

Is this an address autocomplete API?

No. It is a lightweight US address geocoding helper. It is useful for resolving submitted addresses, but it is not a full autocomplete or places search product.