Beyond formatting, it checks deliverability at the premise or sub-premise level, meaning it verifies whether mail can actually be delivered to that specific location. It also returns component-level confidence scores for street, city, state, and ZIP, identifies address types (residential, commercial, PO Box), and provides geocode coordinates.

Yes. Google Address Validation supports addresses globally, though coverage depth varies by country. For US and Puerto Rico addresses, you can enable USPS CASS mode for enhanced validation with carrier-route level data. International addresses get component parsing, standardization, and geocoding based on Google's mapping data.

Go to the Google Cloud Console, create or select a project, enable the Address Validation API from the API library, and generate an API key under Credentials. Enter this key in the Tars Tools configuration. Google charges per validation request, so review their pricing tiers for your expected volume.

Tars processes addresses through Google's API in real time during conversations. The validated result is used to respond to the customer and can be passed to your order management system. Tars retains conversation transcripts per your retention settings, but does not maintain a separate address database.

Yes. The validation response includes metadata that identifies whether the address is residential, commercial, or a PO Box. If your shipping carrier does not deliver to PO Boxes, the agent can immediately ask the customer for an alternative physical address.

ZIP code lookups only verify the postal code exists. Google Address Validation verifies the entire address down to the premise level, corrects misspellings, standardizes formatting, checks deliverability, provides geocode coordinates, and returns component-level confidence scores. It answers whether a package will arrive, not just whether the ZIP is real.

The agent receives a low confidence score or an UNCONFIRMED granularity level. In this case, it prompts the customer to double-check their address, presents the best-guess correction for confirmation, or offers to collect the address components separately (street, city, state, ZIP) for more accurate parsing.

Yes. Google Address Validation handles sub-premise components like apartment numbers, suite numbers, and unit designations. The response includes SUB_PREMISE granularity when it can verify delivery to the specific unit, not just the building. Missing or incorrect unit numbers are flagged in the component analysis.