Validate a commercial street address for freight delivery using the SmartyStreets US Street Address API before LTL shipment creation
domain: smarty.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Send a POST request to the SmartyStreets US Street Address API with the input address fields (street, city, state, ZIP) and include the candidates=1 parameter for single best match
Parse the response dpv_match_code field: Y = confirmed, S = confirmed except secondary (suite/unit), D = confirmed with secondary but secondary is missing, N = not confirmed
For freight-specific validation, check the rdi (Residential Delivery Indicator) field and flag residential addresses for LTL carriers that charge residential delivery accessorials
Extract the standardized address components (delivery_line_1, plus4_code) and replace the user-entered address with the USPS-standardized version before creating the BOL
For addresses returning dpv_match_code N, surface an address correction UI or fallback to a Google Maps geocode for approximate validation with a manual review flag
Known gotchas
The SmartyStreets API returns USPS-standardized addresses; some freight carriers deliver to addresses not in the USPS database (industrial parks, private roads) — a USPS non-match does not always mean undeliverable
The candidates parameter controls how many matching results are returned; for bulk validation jobs use the street-address bulk endpoint with up to 100 addresses per request
RDI classification can be inaccurate for recently converted commercial-to-residential or mixed-use properties; do not apply residential surcharges automatically without a human review step for ambiguous cases
Give your agent this knowledge — and 6,400+ more routes
One MCP install gives any agent live access to the full route map across 2,100+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp