New 42-day free trial
Smarty

Our fast processing speeds

What is the hardest part of processing loads of data? Finding a way to do it fast. Luckily, Smarty is able to process millions of addresses per minute!
Andrew Townsend
Andrew Townsend
 • 
July 8, 2022
Tags

Are you looking to use an API to verify addresses and convert them to latitude and longitude coordinates?

Maybe you also need to standardize addresses in order to de-duplicate records across millions of addresses in your database too. That's right, we're talking about validating, standardizing, and bulk-processing geocodes with a geocoding API.

There are several options out there, so let us tell you how speed sets Smarty apart from the rest.

Smarty is fast. Now, we're not just talking about fast like Usain Bolt. We're not even talking about fast like a race car, or a bullet train. We're talking fast, like an interstellar spacecraft.

Smarty can process over 30,000 address records per second. You read that correctly. That comes out to over 1.5 million a minute. That's fast.

How do we do it?

The secret is creating a scalable system that can't be crippled by extremely large loads. Where most systems begin to grind to a drip when put under the pressure of millions and millions of address lookups sent to their geocoding API, Smarty continues to process at standard high speeds. We spin up new servers to match the usage needs, always staying well ahead of demand.

Can Smarty go faster than that? You betcha!

In the rare case that someone needs more than 10 million geocodes processed in less than five and a half minutes, our enterprise sales team can connect them with a plan that will provide such ludicrous speeds.

Speed may be good, but going that fast without accuracy can be really dangerous. Smarty also has the top address validation system that can handle even seriously distorted addresses. Even at a million and a half a minute, you can expect to have the most accurate address data (even down to rooftop-level geocoding information) with every lookup.

Curious about secondary address points like unit, apartment, or suite? We're good at those, too. You can try your hardest 1,000 addresses in our system and put us to the test. We're confident that you'll be impressed with the speed and accuracy of each address.

In conclusion, Smarty is faster than any other geocoding API tool out there, is rooftop-accurate, and can handle tough addresses.

Subscribe to our blog!
Learn more about RSS feeds here.
rss feed icon
Subscribe Now
Read our recent posts
Ecommerce shipping efficiency tools you need: Address autocomplete and verification
Arrow Icon
We know it’s not New Year's anymore, but we can still push for improvement and efficiency in our lives. Maybe you’ve lapsed on that goal to be healthier or slightly slipped on your new reading and writing regimen. No worries. Not only are we here to remind you to KEEP GOING on whatever goals you have, but we’re also here to give you an easy-to-implement solution that will create shipping efficiency and stop sending packages into the void. I mean, we’re assuming you don’t like wasting money. If you do… that’s how we’re different.
Patient form optimization: The $17.4 million problem
Arrow Icon
Let's start with a number that should make every hospital administrator do a double take: $17. 4 million. That’s how much the average hospital loses annually—just from denied claims due to patient misidentification. This isn’t from equipment costs, not from staffing shortages, and not even from insurance negotiations—just from keeping bad patient data. Surely, our forms aren’t that bad. (Yes, they are, and stop calling me Shirley. )But here’s the reality: According to the 2016 Ponemon Misidentification Report, 30% of hospital claims get denied, and over a third of those denials are caused by inaccurate or incomplete patient information.
The GPS adventures of a distracted developer
Arrow Icon
My name is Jeffrey Duncan, and at the pestering of Smarty’s editor, I’m writing a blog about the many adventures I’ve had in life and how address data has played a big part in them. I met my wife about eight years ago on a dating website. At the time, I lived in Provo, Utah, while she lived in Palmwoods, Australia, on the east coast of Queensland. On this dating app, I entered the area where I was interested in finding someone, about a 25-mile radius of Provo, Utah. I had no intention of leaving the valley, definitely not the state, and certainly not the country.

Ready to get started?