Clean data. Clear results.

Know which contact data is real before you use it

ContactValidate checks the names, emails, phone numbers and mailing addresses you already have, tells you whether they belong to one real person, and when that identity was last active.

Validation resultSample record
  • Jordan AveryName
    Primary match
  • jordan.avery@example.comEmail
    Primary match
  • (555) 010-0147Phone
    Secondary match
  • 1200 Example Ave, Denver, COMailing address
    Unverified
One identityYes
Last seen12 days ago
First seen2017

What we do

One check answers three questions about a contact record.

01

Do these details belong to the person?

Every email, phone number and mailing address is tied to the identity it belongs to, and marked as that person’s primary or secondary value.

JA jordan.avery@…email · primary(555) 010-0147phone · secondaryj.avery@work…email · secondary1200 Example Aveaddress · unverified

02

Does the record hang together?

A record is consistent when no verified value belongs to someone else. One mismatched phone is enough to flag it.

≠ one identity different person

03

Is it still active?

First and last seen dates for the identity show whether a record is current or going stale.

And it hands back clean values.

1200 example ave, denver co 802021200 EXAMPLE AVE, DENVER, CO 80202-0147, US

How it works

From the record you have to a verdict you can act on.

ContactValidate works alongside the systems you already use. Bring contact data from your CRM, a lead list or a signup form.

  1. Send a record

    A name plus any mix of up to 5 emails, 5 phone numbers and 5 mailing addresses, from your code, from Claude or ChatGPT, or by hand in the web app.

    POST /v1/validate
    {
      "name": "Jordan Avery",
      "emails":    [ up to 5 ],
      "phones":    [ up to 5 ],
      "addresses": [ up to 5 ]
    }
    • REST API
    • Claude
    • ChatGPT
    • Web app
  2. We match each value

    Every value is checked against identity data drawn from real online activity and tied to the identity it belongs to, or to none.

    • jordan.avery@…JA
    • (555) 010-0147JA
    • j.avery@work…JA
    • 1200 Example Aveno match
  3. Get a verdict per field

    Each value comes back labelled, with a standardized version and the identity’s first and last seen dates, so you know what to keep, fix or drop.

    Primary match×1

    Secondary match×2

    Unverified×1

    One identity · last seen 12 days ago

1 credit per check, whatever the verdict. If we can’t get an answer, the credit is refunded automatically. What a check can and can’t tell you.

See pricing

Use it where you work

The same check, the same price and the same result through every channel.

REST API

Create a key in the web app and send POST /v1/validate.

{
  "name": "Jordan Avery",
  "emails": [
    "jordan.avery@example.com"
  ],
  "phones": [
    "+15550100147"
  ]
}

API reference

Claude and ChatGPT

Add ContactValidate as a connector, sign in once, and ask your assistant to validate a contact. It sees the price before it spends a credit.

Connect an AI client

Web app

Run a single check by hand, look back through your results, manage API keys and try the API in the playground.

Open the web app

Who uses it

Teams that own contact data and need to know which of it is real.

Note: ContactValidate is not a “consumer reporting agency” as defined in the Fair Credit Reporting Act (“FCRA”), and its results are not “consumer reports” as defined in the FCRA. Results may not be used as a factor in determining eligibility for credit, insurance, employment, housing or any other purpose for which a consumer report may be used under the FCRA.

  1. Before a campaign

    Revenue and marketing ops

    Check CRM records and imported lists so outreach goes to details that belong to the right person.

    Watch forIdentities not seen in years

  2. On every form fill

    Lead generation

    Screen form fills and purchased leads for made-up or mismatched details before they reach a sales team or a client.

    Watch forDetails that tie to no one

  3. Before outreach

    Collections

    Confirm which phone numbers, emails and addresses on file still tie to the account holder.

    Watch forNumbers that belong to someone else

  4. At account creation

    Signup and onboarding

    Details that tie to no one, or to several different people, are worth a second look before you approve an account.

    Watch forRecords that don’t hang together

  5. Before a mail drop

    Real estate

    Keep buyer, seller and owner lists current so calls and mailers reach the people you mean to reach.

    Watch forSecondary and unverified addresses

  6. Mid-task

    AI agents and workflows

    Give Claude, ChatGPT or your own agent a validation tool it can call on its own, with the price stated before every call.

    Watch forDetails that belong to someone else

Have questions?

Ask about volume, a pilot, or whether ContactValidate fits your data. Email support@contactvalidate.com and a person will reply.

Email us