Data Quality
Is this data valid, real, and worth acting on?
1.Location Type — classify_location_type
Classifies an address as residential, commercial, or industrial from map and image evidence.
Inputs
Field | Required | Description |
|---|---|---|
address | ✅ | Full address |
llm | — | Model override |
Outputs
Field | What you get |
|---|---|
location_type | Land-use class |
image_link | Map or image reference URL |
errors | Any issues that came up |
🔗 Chain it: find_company_email_phone_address → classify_location_type → icp_score
2.IP Geolocation — enrich_ip_address
Looks up IP geolocation and network details.
Inputs
Field | Required | Description |
|---|---|---|
ip | ✅ | IP address |
Outputs
Field | What you get |
|---|---|
city | Geo city |
country | Geo country |
org | ISP or organization |
coordinates | Lat/lng string |
errors | Any issues that came up |
🔗 Chain it: enrich_ip_address → icp_score
3.Contact Phone Validation — phone_intel
Produces a callability recommendation with confidence and provider payloads.
Inputs
Field | Required | Description |
|---|---|---|
phone | ✅ | Phone number |
person_name | — | Person context |
company_name | — | Company context |
skip_dnc | — | Skip DNC/TCPA check |
Outputs
Field | What you get |
|---|---|
recommendation | CALL or SKIP |
confidence | Confidence (0–100) |
primary_reason | One-line rationale |
verdict | Structured verdict object |
errors | Any issues that came up |
🔗 Chain it: find_phone_waterfall → phone_intel → validate_biz_phone
4.Business Phone Validation — validate_biz_phone
Normalizes phone to E.164 format and classifies the likely business contact role.
Inputs
Field | Required | Description |
|---|---|---|
phone | ✅ | Business phone input |
Outputs
Field | What you get |
|---|---|
output | Cleaned E.164 phone |
status | Role heuristic label |
errors | Any issues that came up |
🔗 Chain it: find_company_email_phone_address → validate_biz_phone → phone_intel