Start with an address

Try one address

Enter one U.S. address on the homepage. Your first address does not require an account. Review the status and postal evidence, then expand Address Intelligence for the same address where a canonical location can be established. Nearby datasets have their own coverage limits.

Submitting another address prompts you to create an email account or sign in. Your existing console remains the place for ongoing work.

Process a spreadsheet

1. Open spreadsheet jobs in the console and sign in if needed.
2. Upload a CSV or Excel file and inspect the mapped address columns before processing.
3. Review the available account allowance and the number of rows selected for processing.
4. Review status and evidence in the completed results. Keep unresolved records for review.

Street address

Map the column containing the house number, street and unit. Keep unit information with the address.

City and state

Map these components when available. More complete inputs reduce avoidable ambiguity.

ZIP

Keep ZIP codes as text to preserve leading zeroes.

Original row identifiers

Keep your own record identifier so you can reconcile downloaded results with the original file.

Review and download results

Download available results from the completed console job. Keep the original address alongside returned components. A corrected format, postal range match, physical point and delivery confirmation represent different evidence. A result with no coordinates is not a map-ready location.

Do not silently overwrite ambiguous or unresolved records. Review any changed street, locality, ZIP or unit before applying a consequential update.

Connect your API

Create a key in console API keys and make the request from your server. The external API uses address components and returns result, ax_* and evidence fields.

curl --request POST 'https://api.addrex.dev/v1/validate' \
  --header "Authorization: Bearer $ADDREX_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
  "street": "135 W Ravine Rd",
  "city": "Kingsport",
  "state": "TN",
  "zip": "37660",
  "include_quality": true
}'

Read the complete request, response and error reference. The public API contract differs from the application's internal console adapter.

Current console Beta limits

Console lookup limit: 1,000 per day. Spreadsheet limit: 10,000 rows per day. Both draw from shared daily usage.

Daily usage is shared across console lookup and spreadsheet processing; these are not additive allowances. Your console shows the next daily reset time.

Email verification is required to activate Beta processing.

External API usage is checked by the API service and may differ from console Beta usage. Your account and returned usage headers provide context. View plans and availability.

Autocomplete

Autocomplete is separately controlled and is not included in the anonymous first-address experience or advertised console Beta allowance. Contact Addrex about access before integrating it.

When something goes wrong

If a request fails, retain your input and try again after a temporary service error. Do not repeatedly submit a failed request in a tight loop. For account or integration help, use contact options. See service availability information before starting a large job.