MPPtempoquality 0.88

Whitepages person search via micropayment — find people by name, phone, or address at $0.44/request.

Price
$0.44 / call
Protocol
mpp
Verified
no

What it does

The Whitepages Person Search endpoint on StableEnrich lets you look up individuals by name, phone number, or street address. It returns structured data including current and historical addresses, phone numbers, emails, date of birth, LinkedIn URL, job title, company name, relatives, owned properties, and deceased status. The endpoint accepts optional filters such as state_code (two-letter abbreviation), city, zipcode, age range (min_age/max_age), and radius (up to 100 miles). An excludeFields parameter lets you trim the response payload.

This endpoint is part of StableEnrich, a pay-per-request gateway that aggregates multiple data providers (Apollo, Exa, Firecrawl, Google Maps, Serper, Whitepages, Clado, Minerva, Hunter, Reddit, Influencer, Cloudflare) behind a single origin. No API keys or subscriptions are required; authentication is handled via micropayment using the MPP (Tempo) or x402 protocol on Base mainnet, Solana, or Tempo. The fixed price is $0.44 per request. Payments settle on-chain and are not charged on 5xx errors.

The endpoint is a POST to https://stableenrich.dev/api/whitepages/person-search. A full OpenAPI 3.1 schema is published, including both request and response shapes. The response returns a persons array with rich nested objects for addresses, phones, relatives, and properties. The probe did not capture a 402 challenge on HEAD/GET (the endpoint only accepts POST), but the OpenAPI spec and guidance confirm it is live and priced.

Capabilities

person-lookupreverse-phone-lookupaddress-lookuppeople-searchwhitepagescontact-enrichmentproperty-ownershiprelative-discoveryage-filteringradius-searchmicropayment-authmpp-tempox402

Use cases

  • Finding contact information (phone, email, address) for a person by name and state
  • Reverse phone number lookup to identify the owner
  • Verifying a person's current address or finding historical addresses
  • Discovering relatives and household members for a given individual
  • Background research combining person data with property ownership

Fit

Best for

  • Agents that need US consumer contact data without API key setup
  • One-off or low-volume person lookups where subscription pricing is wasteful
  • Automated research pipelines that combine people data with other StableEnrich endpoints

Not for

  • High-volume batch lookups where per-request cost adds up quickly ($0.44 each)
  • International person search — Whitepages data is US-focused
  • Use cases requiring real-time identity verification or KYC compliance

Quick start

POST https://stableenrich.dev/api/whitepages/person-search
Content-Type: application/json

{
  "first_name": "John",
  "last_name": "Smith",
  "state_code": "CA"
}

Example

Request

{
  "last_name": "Smith",
  "first_name": "John",
  "state_code": "CA"
}

Response

{
  "persons": [
    {
      "id": "Person.abc123",
      "name": "John Smith",
      "emails": [
        "john.smith@example.com"
      ],
      "phones": [
        {
          "type": "mobile",
          "score": 90,
          "number": "+14155551234"
        }
      ],
      "aliases": [
        "Johnny Smith"
      ],
      "is_dead": false,
      "job_title": "Software Engineer",
      "relatives": [
        {
          "id": "Person.def456",
          "name": "Jane Smith"
        }
      ],
      "company_name": "Acme Corp",
      "linkedin_url": "https://www.linkedin.com/in/johnsmith",
      "date_of_birth": "1985-03-15",
      "current_addresses": [
        {
          "zip": "94105",
          "city": "San Francisco",
          "state": "CA",
          "full_address": "123 Main St, San Francisco, CA 94105"
        }
      ]
    }
  ]
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.88/ 1.00

Full OpenAPI 3.1 schema with detailed request/response shapes, clear USD pricing ($0.44/request), comprehensive guidance docs, and examples are all present. The probe did not capture a 402 MPP challenge because the endpoint only accepts POST (HEAD/GET returned 405), but the OpenAPI spec and pricing table confirm it is live and correctly configured.

Warnings

  • Probe returned 405 on HEAD and GET because this endpoint only accepts POST; this is expected, not an outage.
  • Whitepages data is primarily US-focused; international coverage is limited or absent.
  • At $0.44 per request this is one of the more expensive endpoints on StableEnrich; cost can accumulate quickly for batch use.
  • This endpoint deals with personal data (addresses, phone numbers, relatives) — ensure compliance with applicable privacy regulations.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:23:44Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access