City Name Validation

GeoDB Cities holds reference data on cities, regions, and countries that a form or record can check an entry against. A Beam agent reads a city or region value entered on an incoming record, such as a shipping address or a signup form, and checks it against GeoDB Cities within the rules a team has approved, such as allowing for common spelling variants. A valid entry gets confirmed on the record automatically. An entry with no close result, or more than one plausible result, gets sent to a person to confirm rather than the agent picking one.

Population and Region Filtering

GeoDB Cities returns attributes like population and administrative region alongside a city name, which supports filtering a list down to relevant places. A Beam agent reads a request for cities meeting an approved filter, such as a minimum population within a given country, and returns the corresponding set to populate a dropdown or reference list inside a linked tool. The agent does not decide which filter to apply: that threshold is set by a person in advance. Any request for a filter outside the agreed set gets routed back to a person to define first.

Address Field Standardization

Address records often carry city and region names typed inconsistently, which complicates reporting and shipping. A Beam agent reads an address field on an incoming record, looks up the closest GeoDB Cities entry, and writes back a standardized city and region name once the confidence clears a threshold a team has approved. Records below that threshold keep their original entry and get flagged for a manual check. This keeps the standardization limited to clear cases, and a person handles anything ambiguous, such as a city name shared by multiple countries, before it is changed.