Address Reference Registry
Reconcile sourced address components, delivery sites and historical aliases into independently verified registry editions.
Application guideVerifying your session…
Using Address Reference Registry
Resolve component-level source disagreements, verify address changes and publish reference datasets valid at a chosen date.
Component provenance · Historical alias search · Verified changes · Versioned dataset editions
- Inputs and working data
- Permanent identifiers, sourced baseline values, dated observations, per-field authority choices, effective versions, aliases, delivery/access points and edition hashes.
- Working in the editor
- Baseline and admission, source observations, per-component reconciliation, signed change verification and edition publication.
- What can I produce?
- Historical address and delivery search, traceable verified changes, versioned dataset JSON, manifest checksum and field-level source export.
- What are the limits?
- 1500 baseline addresses, 60 aliases and 40 delivery points per address. Search uses normalized user-provided names and effective dates.
- Example
- Reconcile a survey street and postal source, sign under a second account, find the new version by its former name, verify the ZIP checksum and reopen.