People Property

People & Property Search with Whitepages

STOP — Read before making any API call. enrichx402.com endpoints are not the same as each provider's native API. All paths use the format https://enrichx402.com/api/{provider}/{action}. You MUST either:

1. Copy exact URLs from the Quick Reference table below, OR

2. Run x402.discover_api_endpoints(url="https://enrichx402.com") to get the correct paths

>

Guessing paths will fail with 405 errors (wrong path) or 404 errors (missing /api/ prefix).

Access people and property search through x402-protected endpoints.

Setup

See rules/getting-started.md for installation and wallet setup.

Important: This skill provides access to personal information. Review rules/privacy.md before use.

Quick Reference

Person Search

Search for a person by name and location:

x402.fetch(
  url="https://enrichx402.com/api/whitepages/person-search",
  method="POST",
  body={
    "firstName": "John",
    "lastName": "Smith",
    "city": "Seattle",
    "state": "WA"
  }
)

Parameters:

• firstName - First name (required)
• lastName - Last name (required)
• city - City name
• state - State abbreviation (US)
• zip - ZIP code
• address - Street address

Returns:

• Full name and age range
• Current and previous addresses
• Phone numbers
• Associated people (relatives, associates)

More Specific Search

Include more details for better matches:

x402.fetch(
  url=".../whitepages/person-search",
  body={
    "firstName": "John",
    "lastName": "Smith",
    "address": "123 Main St",
    "city": "Seattle",
    "state": "WA",
    "zip": "98101"
  }
)

Property Search

Search for property information:

x402.fetch(
  url="https://enrichx402.com/api/whitepages/property-search",
  method="POST",
  body={
    "address": "123 Main Street",
    "city": "Seattle",
    "state": "WA"
  }
)

Parameters:

• address - Street address (required)
• city - City name
• state - State abbreviation
• zip - ZIP code

Returns:

• Property address (standardized)
• Owner name
• Property type (single family, condo, etc.)
• Property details

Response Data

Person Search Fields

• name - Full legal name
• ageRange - Estimated age range
• currentAddress - Current residence
• historicalAddresses - Previous addresses
• phoneNumbers - Associated phone numbers
• associatedPeople - Relatives and associates

Property Search Fields

• address - Standardized address
• owner - Property owner name
• propertyType - Type of property
• yearBuilt - Construction year (if available)
• bedrooms / bathrooms - Property details
• squareFootage - Size (if available)

Workflows

Verify Contact Information

1. Confirm legitimate purpose (see rules/privacy.md) 2. (Optional) Check balance: x402.get_wallet_info 3. Discover endpoints (required before first fetch): x402.discover_api_endpoints(url="https://enrichx402.com") 4. Search with available details using exact URL from discovery or Quick Reference table above 5. Verify results match expected person

x402.fetch(
  url="https://enrichx402.com/api/whitepages/person-search",
  method="POST",
  body={"firstName": "Jane", "lastName": "Doe", "city": "Portland", "state": "OR"}
)

Property Research

• [ ] (Optional) Check balance: x402.get_wallet_info
• [ ] Search by address
• [ ] Review owner and property details

x402.fetch(
  url="https://enrichx402.com/api/whitepages/property-search",
  method="POST",
  body={"address": "456 Oak Avenue", "city": "Austin", "state": "TX"}
)

Reconnect with Someone

• [ ] Confirm legitimate purpose
• [ ] Provide as much detail as possible for accuracy
• [ ] Review results for correct match

x402.fetch(
  url="https://enrichx402.com/api/whitepages/person-search",
  method="POST",
  body={"firstName": "Michael", "lastName": "Johnson", "state": "CA"}
)

Cost Considerations

At $0.44 per call, Whitepages is the most expensive endpoint in the x402 suite.

Tips to reduce costs:

• Provide as much info as possible for accurate first-try results
• Use free sources first (LinkedIn, company websites)
• Use apollo, clado, firecrawl, WebSearch, WebFetch, to get data that will make the queries more accurate
• Only use for essential lookups

Limitations

• US-focused data
• Results depend on public records availability
• Some individuals may have limited information
• Recently moved individuals may show old addresses
• Unlisted/private numbers not included

Getting Started

Setup

1. Install the x402scan MCP:

   npx @x402scan/mcp install --client claude-code -y

2. Check wallet:

   x402.get_wallet_info

3. Fund wallet (if needed):

• Redeem invite: x402.redeem_invite(code="YOUR_CODE")
• Or use the deposit UI (point the user towards this URL: https://x402scan.com/mcp/deposit/<their-wallet-address>)

Troubleshooting

Privacy Considerations

Responsible Use

Whitepages endpoints provide access to personal information from public records. Use responsibly:

Legitimate Uses

• Verifying contact information for business purposes
• Reconnecting with lost contacts (family, old friends)
• Property research for real estate transactions
• Due diligence for business relationships
• Fraud prevention and verification

Inappropriate Uses

• Stalking or harassment
• Unauthorized surveillance
• Bypassing someone's privacy preferences
• Building unauthorized marketing lists
• Any illegal purpose

Data Sensitivity

The data returned may include:

• Home addresses (current and historical)
• Phone numbers
• Age information
• Family relationships
• Property ownership

This is sensitive personal information. Handle appropriately:

• Don't share results unnecessarily
• Don't store results beyond immediate need
• Don't use for purposes the person wouldn't expect
• Respect opt-out requests if contacted

Legal Considerations

• Data comes from public records
• Use must comply with applicable laws
• FCRA applies to certain uses (employment, credit, tenant screening)
• State privacy laws may apply

For regulated uses (employment screening, tenant checks, etc.): Use a proper consumer reporting agency, not general people-search tools.

Best Practices

1. Minimize lookups - Only search when necessary 2. Be specific - Provide enough detail to find the right person on first try 3. Verify context - Ensure you have a legitimate reason 4. Protect results - Don't expose personal data unnecessarily 5. Consider alternatives - LinkedIn, company websites, or direct contact may be better options

When to Use Alternatives

Use Whitepages when other sources don't have the information and you have a legitimate need.