Unify and manage your data

Address Enricher

Learn about what the Address Enricher Agent does and when to use it.

The Address Enricher agent validates and corrects problematic addresses in Organization profiles using evidence from authoritative sources.

Who is it for?

Data Steward Data Product Owner System Administrator

For more information, see About roles.

Why would I use it?

To ensure address accuracy and resolve issues with ambiguous or incomplete location data.

When and where would I use it?

Run the agent when addresses are flagged as Partially Verified" or "Ambiguous". Operates within AgentFlow.

How does it support business goals?

Improves data trust and downstream reliability for matching, segmentation, and compliance reporting.

Core capabilities

  • Detect incomplete or ambiguous addresses
  • Research across ≥3 sources
  • Update Locations with evidence
  • Create new entity if address differs entirely
InputsOutputs

Entity Type Selection (Organization or equivalent)

Verification Status Filter (Partially Verified or Ambiguous)

Your Decisions (when evidence is unclear or conflicts arise)

Continuation Confirmation (whether to process next record)

Organization List (entities with problematic addresses)

Current Address Details (existing Location data)

Research Evidence (URLs from 3+ authoritative sources)

Proposed Changes (before/after comparison table)

Update Confirmation (success/failure status)

Post-Update Validation (verified corrected values)

Audit Trail (source URLs and provenance)

Processing Summary (what was changed and why)

Watch how it works

Watch how the Address Enricher agent helps you investigate and update incomplete and/or incorrect addresses in your profiles. This short demo shows how the agent uses evidence from multiple trusted sources to validate, compare, and apply accurate address data. You'll learn how to resolve flagged locations in AgentFlow without overwriting system-managed fields.

Safeguards, permissions, and governance

  • Requires ≥3 corroborating sources
  • Preserves system fields
  • Requires authenticated access

Limitations and edge cases

  • Processes one Organization at a time
  • Skips if validation threshold is not met