New 42-day free trial Get it now
Smarty

When to use strict vs enhanced matching in your address API

When to use strict vs enhanced matching in your address API
Updated December 11, 2025
Tags
When to use strict vs enhanced matching in your address API

In our recent webinar, we invited Easton Gibson, one of our US Street API software engineers, to discuss key features of address validation and give insights into the functionalities of both strict and enhanced modes.

In this blog, we'll cover:

Understanding strict mode

Strict mode is precisely what it sounds like—it rigorously validates addresses against the official USPS database, ensuring that only fully accurate, postal-verified addresses are accepted. This mode is typically used for operations requiring high precision, such as legal or financial document dispatch.

For example, if you enter a known address into Smarty's address tools with strict mode, you'll see that it processes and standardizes address data, rejecting any entry that doesn't perfectly match USPS records.

However, while most people use strict mode for its reliability in confirming that an address is recognized by the USPS, its rigidity creates problems.

Introduction to enhanced mode

Enhanced mode is better than strict mode because it uses fuzzy logic, machine learning, and generally more information to provide a holistic story for each address. This mode is designed to capture and validate addresses that might not be part of the USPS database. These are known as non-postal addresses and include things such as newer developments or rural locations.

Enhanced mode’s ability to handle non-postal addresses is a significant benefit. For instance, it can identify and validate non-postal addresses and correct common address mistakes, giving you workable information instead of just an unknown result.

Enhanced mode provides everything strict mode will, but with more information about why an address does or doesn’t match. Instead of giving a “yes/no” response, it may give a “yes, if” response or “no, because.”

You can play with the enhanced mode results on the US Street API demo page.

FAQ for enhanced mode

What are the main sources for non-postal addresses in Smarty’s database?
The sources for non-postal addresses include several proprietary datasets that Smarty™ has access to, which are part of our "secret sauce." For detailed information, you can reach out to an account executive.

If I want results only from USPS addresses, should I use enhanced mode and filter out non-postal matches, or stick with strict mode?
Using enhanced mode is recommended even if you require only USPS addresses. Enhanced mode's aggressive matching strategy means it can handle typographical errors and other common discrepancies better than strict mode. Results that are non-postal will be clearly indicated, allowing easy filtering while still benefiting from enhanced mode's robust matching capabilities.

How does enhanced mode handle inputs with significant errors or typos, especially in critical components like the street name or number?
Enhanced mode is designed to be more forgiving of errors, including significant misspellings. It uses sophisticated algorithms to interpret and correct errors where possible, differentiating it from strict mode, which requires exact matches. However, there are limits; if an input is too far off from any real address data, even enhanced mode may not be able to make a correct match.

Webinar about "enhanced mode"

If you'd like to view the full webinar recording and the demos given, you can view that here:

Subscribe to our blog!
Learn more about RSS feeds here.
Read our recent posts
Smarty customers avoid USPS rate limiting
Arrow Icon
TLDR: Smarty customers won’t feel a thing from the new USPS API restrictions because Smarty doesn’t depend on USPS’s real-time APIs to do address verification. We’ve always used our own, powerful, hyper-accurate data to back our tools and support client needs. While USPS is capping its address verification service at 60 requests per hour and retiring the legacy Web Tools API on January 25, Smarty keeps verifying addresses at full speed on our own infrastructure. We ingest USPS data updates monthly and run verification internally, so USPS API changes, rate limits, or even a temporary USPS outage don’t ripple into your workflows.
Provider data accuracy: Regulatory compliance and hidden network risks
Arrow Icon
Welcome to part one of our new blog series on provider location data—an exploration into the messy, high-stakes world of healthcare compliance, address accuracy, and network adequacy. To kick things off, we sat down with Dave Medlock, founder of Maven One Health and a contributing thought leader, to discuss why clean provider data is essential for achieving peak regulatory compliance and meeting requirements with ease, thereby avoiding serious consequences if it isn’t done correctly. Here’s what he had to say about understanding CMS, state DOIs, continuous audits, rosters, data decay, messy inputs, and the future of address data itself.
Always on; always Smarty: High availability design and engineering best practices
Arrow Icon
When the digital world falters, our goal is simple: stay steady for our customers. At Smarty, reliability isn’t a bragging point, but rather a promise. We’ve built a platform designed to keep running even when others stop, using a vendor-agnostic, redundant infrastructure grounded in engineering best practices that weather disruptions with quiet consistency. Our customers depend on uninterrupted address data services. And, we take that trust seriously. And because we trust you, we’re offering a 42-day free trial on every product.

Ready to get started?