verification? yes
check it out here https://geteasypost.com/docs
check it out here https://geteasypost.com/docs
Your service is doing more than simple verification. Verification by its nature would result in a boolean. Your service is suggesting a better address (which is what I'd call normalization). e.g.
curl https://www.geteasypost.com/api/address/verify \
-u cueqNZUb3ldeWTNX7MU3Mel8UXtaAMUi: \
-d 'address[street1]=388 Townshende Ave' \
-d 'address[street2]=Unit 20' \
-d 'address[city]=San Francisco' \
-d 'address[state]=CA' \
-d 'address[zip]=94107'
yields: {"address":{"street1":"388 TOWNSEND ST APT 20","city":"SAN FRANCISCO","state":"CA","zip":"94107"}}
Anyhow, semantics aside, are you going to make it fuzzier or this is based entirely on USPS' api? "388 Townsend San Fran"
Would yield the same as above. Addresses are inherently dirty data and there aren't any decent/affordable/legal services that offer this. You can use Google Maps Geocoder or Yahoo Placefinder but both have fairly strict quotas and are only intended (legally speaking) for use with their mapping products. USPS/FedEx/UPS are also restricted unless you're shipping with them.Edit - Yahoo is actually letting people pay very respectable rates for their PlaceFinder service now. This is great: http://developer.yahoo.com/boss/geo/
1) They are abusing the USPS api and charging access for it.
2) The USPS resolver sucks anyhow. "388 Townsend San Fran" yields an error. Google & Yahoo both correctly match it.
3) Their pricing is pretty expensive, imo.