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.