Validate, standardize, and geocode U.S. addresses—fast.
API-first address normalization and reference validation with explainable match codes, confidence scoring, and precise coordinates. Real-time and batch from the same engine.
Built for real-time APIs and high-volume batch workflows.
No DPV claims. Reference-validated against our national dataset.
Sample Request
// Input
1600 pennsylvania ave nw
washington dc 20500
Response
{
"validation_status": "VERIFIED",
"match_code": "STANDARDIZED",
"confidence": 0.98,
"line1": "1600 Pennsylvania Ave NW",
"city": "Washington",
"state": "DC",
"zip": "20500-0005",
"lat": 38.8977,
"lon": -77.0365
}Built for teams that care about clean data
Explainable Outputs
Every result includes match codes and reason codes so you know exactly what happened.
Real-time + Batch
Same validation engine powers both instant API calls and bulk file processing.
Clear Retention Controls
Configure how long batch data is retained. Real-time requests have no storage.
Bad addresses are expensive
- 1
Failed deliveries and returns
Packages bounce, shipments delay, and customers get frustrated.
- 2
Onboarding friction
Invalid addresses create signup abandonment and downstream data problems.
- 3
Broken analytics
Duplicate and malformed addresses corrupt your data, skewing insights.
Addrex fixes that
Catch errors before they ship
Validate in real-time at checkout, signup, or data entry.
Clean your existing database
Upload bulk files and get standardized, deduplicated records back.
Understand every result
Explainable codes tell you what changed and why—no guesswork.
Everything you need for address quality
A complete toolkit for validating, standardizing, and enriching address data.
Extract addresses from messy text
Paste a block of text and Addrex will detect one or more addresses, normalize them, validate against our reference dataset, and return standardized results with match codes.
Perfect for CRM notes, insurance claims, customer support tickets, and data migrations where addresses are buried in unstructured content.
Example Input
"Send docs to 123 N Main St, Austin TX or warehouse at 456 Elm Rd, Round Rock."
Result
2 addresses found
1. 123 N Main St, Austin, TX 78701 — Verified
2. 456 Elm Rd, Round Rock, TX 78664 — Verified
Reference coverage & validation approach
Addrex validates addresses against a continuously maintained national reference dataset.
We do not claim USPS DPV or CASS certification. When an address cannot be verified, we return clear reason codes and support ingestion into our reference update workflow.
How it works
Three simple steps to validated, geocoded addresses.
Send
Submit an address via API or upload a file through our portal.
Score
We parse, standardize, validate against our dataset, and geocode.
Return
Get clean data with confidence scores, coordinates, and reason codes.
Batch output preview
Upload a file, get structured results with validation status and coordinates.
| Input Address | Status | Match | Confidence | Lat | Lon |
|---|---|---|---|---|---|
| 1600 penn ave, washinton dc | Verified | Corrected | 0.94 | 38.8977 | -77.0365 |
| 350 5th Ave, New York, NY 10118 | Verified | Exact | 0.99 | 40.7484 | -73.9857 |
| 1 infinite loop cupertino | Verified | Corrected | 0.96 | 37.3318 | -122.0312 |
| 123 fake street nowhere | Not Found | None | 0.00 | 0.0000 | 0.0000 |
Built for developers
Clean REST APIs with predictable responses. Integrate in minutes, not days.
https://api.addrex.io · https://docs.addrex.dev
curl -X POST https://api.addrex.io/v1/validate \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"address": {
"line1": "1600 Pennsylvania Ave NW",
"city": "Washington",
"state": "DC",
"zip": "20500"
}
}'{
"validation_status": "VERIFIED",
"match_code": "STANDARDIZED",
"confidence": 0.98,
"standardized": {
"line1": "1600 Pennsylvania Ave NW",
"city": "Washington",
"state": "DC",
"zip5": "20500",
"zip4": "0005"
},
"geocode": {
"lat": 38.8977,
"lon": -77.0365,
"quality": "ROOFTOP"
},
"reason_codes": []
}Security & Privacy
We take data security seriously. Here's how we protect your information.
TLS encryption in transit
All API communications are encrypted using TLS 1.2+.
API key authentication
Secure, revocable API keys with usage monitoring.
Redacted logging recommended
We recommend and support redacted address logging for compliance.
Configurable batch retention
Set custom retention periods for batch processing data.