SafeStreets

Quality 88 / 100good

8 tools, about 2,995 tokens to load them all · tool set 45695e0fd9a9 · tools last changed 2026-10-22 · checked 2026-11-14 07:03 UTC

Tool changes

• 2026-10-22search_neighborhoodschangeddescription
  before

  Ranked neighborhood search across every US neighborhood (202,000+), for "where should I move" questions. Use this when someone is relocating and has not picked a town yet: filter to a county set, a metro, a state, a home-price ceiling or a walkability floor, then rank by walkability, transit, zero-car share, demand or home value. Each row carries median home value, median income, price-to-income ratio, commute mode shares, zero-car household share, and where available year-over-year home value growth and property tax rate — so walkability can be read alongside what living there costs. Counties are addressed by 5-digit state+county FIPS codes because county names repeat across states (there are Delaware Counties in PA, OH, NY and IN). Example: Chester PA 42029, Delaware PA 42045, Montgomery PA 42091, New Castle DE 10003. walkabilityIndex is the EPA National Walkability Index on its 1-20 scale, with a national percentile beside it, and sort_by "walk" ranks on it. It is not the 0-100 SafeStreets score; for that, follow up with get_walkability_score on a specific address.

  after · 92% of words in common

  Ranked neighborhood search across every US neighborhood (202,000+), for "where should I move" questions. Use this when someone is relocating and has not picked a town yet: filter to a county set, a metro, a state, a home-price ceiling or a walkability floor, then rank by walkability, transit, zero-car share, demand or home value. Each row carries median home value, median income, price-to-income ratio, commute mode shares, zero-car household share, and where available year-over-year home value growth and property tax rate — so walkability can be read alongside what living there costs. Counties are addressed by 5-digit state+county FIPS codes because county names repeat across states (there are Delaware Counties in PA, OH, NY and IN). Example: Chester PA 42029, Delaware PA 42045, Montgomery PA 42091, New Castle DE 10003. walkabilityIndex is the EPA National Walkability Index on its 1-20 scale, with a national percentile beside it, and sort_by "walk" ranks on it. It is a different scale from the 0-100 SafeStreets score, which comes from scoring one address.

• 2026-10-22score_manychangeddescription
  before

  Score up to 10 US locations in one request. Use this for a list: properties, branches, listings, sites. For two to a handful of places where the question is which is better, compare_locations answers it directly instead. Each location counts as one call against your allowance, so a list of ten costs ten. A location that cannot be resolved is reported in errors rather than failing the request.

  after · 77% of words in common

  Score up to 10 US locations in one request. Use this for a list: properties, branches, listings, sites. Each location counts as one call against your allowance, so a list of ten costs ten. A location that cannot be resolved is reported in errors rather than failing the request.

• 2026-10-22get_walkability_scorechangeddescription, input schema
  before

  Score a US location on how good and how safe it is to walk, from a street address or from latitude/longitude. Call this when someone asks whether a place is walkable, how safe it is to walk, whether they could live somewhere without a car, how a neighborhood compares to another on foot, or when evaluating a specific address or property for walkability or pedestrian risk. Pass "address" when you have an address. Do not convert an address to coordinates yourself: coordinates recalled from memory land somewhere else, and this tool will score that other place and return a confident number for it. When an address is used, the reply carries resolvedFrom with the address that was actually matched, so check it before quoting the score. Returns a JSON object: overallScore 0-100 composite displayScore the same score as 0-10, which is how SafeStreets presents it grade A to F tier plain label, e.g. "Very walkable", "Car-dependent" confidence 0-100, how much underlying data was available for this point dataSources the sources that fed this specific result components four scored sub-dimensions, each with a 0-100 score and the individual metrics behind it: dailyReach errands reachable on foot streetSafety street design and pedestrian crash risk transitReach usable transit access walkingComfort shade, heat, air quality, surface plus networkDesign, which carries its metrics (network density, intersection density, block length, dead-end ratio) but reports score 0 at weight 0, so it does not contribute to the composite. Read its metrics, not its score. The keys safety, environmentalComfort and densityContext are backward-compatibility aliases of streetSafety, walkingComfort and dailyReach. They duplicate those objects rather than adding signal. The per-component metrics are the point: you can re-weight or rebuild the composite yourself instead of trusting one number. Coverage and limits: United States only. Pedestrian crash inputs are county-level, so two nearby points can share crash figures. Where the underlying crash record is missing, the safety component is reported as unavailable rather than guessed, and confidence drops accordingly. This does not return driving directions, transit timetables, crime statistics, or property listings.

  after · 87% of words in common

  Score a US location on how good and how safe it is to walk, from a street address or from latitude/longitude. Call this when someone asks whether a place is walkable, how safe it is to walk, whether they could live somewhere without a car, how a neighborhood compares to another on foot, or when evaluating a specific address or property for walkability or pedestrian risk. The server geocodes an address itself. Coordinates estimated from memory can land on a different place, which then gets a confident score of its own. When an address is given, the reply carries resolvedFrom with the address that was matched. Returns a JSON object: overallScore 0-100 composite displayScore the same score as 0-10, which is how SafeStreets presents it grade A to F tier plain label, e.g. "Very walkable", "Car-dependent" confidence 0-100, how much underlying data was available for this point reportUrl the full SafeStreets report for this point: map, metrics, PDF dataSources the sources that fed this specific result components four scored sub-dimensions, each with a 0-100 score and the individual metrics behind it: dailyReach errands reachable on foot streetSafety street design and pedestrian crash risk transitReach usable transit access walkingComfort shade, heat, air quality, surface plus networkDesign, which carries its metrics (network density, intersection density, block length, dead-end ratio) but reports score 0 at weight 0, so it does not contribute to the composite. Read its metrics, not its score. The keys safety, environmentalComfort and densityContext are backward-compatibility aliases of streetSafety, walkingComfort and dailyReach. They duplicate those objects rather than adding signal. The per-component metrics are the point: you can re-weight or rebuild the composite yourself instead of trusting one number. Coverage and limits: United States only. Pedestrian crash inputs are county-level, so two nearby points can share crash figures. Where the underlying crash record is missing, the safety component is reported as unavailable rather than guessed, and confidence drops accordingly. This does not return driving directions, transit timetables, crime statistics, or property listings.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.