MarketplaceVerification

Employer Verification

Confirm users actually work at the organizations they claim before granting marketplace access.

Email identity · 1,000 credits per lookup · no monthly fee

Claims:Works at Acme Corp
d.kim@acmecorp.com
Employment confirmed

The problem

Your platform grants access based on where people claim to work, and claims are free. A 'Google engineer' with a personal Gmail and no verifiable footprint is a moderation problem you'll meet later, in public.

With Encrata

Cross-check the claim against the identity behind the email. A corporate address that resolves to a matching person, role and company is strong verification; a mismatch is a signal to ask for more proof before granting the badge, the community access, or the discount.

How it works

1

Send the address

Call the identity endpoint with just an email address, no name, no company, nothing else required.

2

We resolve the person

Encrata matches the address against public profiles and returns name, role, company, location and social accounts.

3

Use the profile

Route, personalise, verify or investigate with a full picture of who is behind the address. Fields you ask for are the fields you get.

One call, structured answer

Employer Verification runs on the email identity lookup at 1,000 credits per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • A match on 99.86% of addresses, near-zero dead lookups
  • Every field is labelled found or not found, so you never guess what to trust
  • Ask only for the fields you need with the fields parameter
  • One API call replaces minutes of manual research per contact
Terminal
curl -X POST "https://encrata.com/api/agent/email-identity" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "jane@example.com"}'
response.json
{
"email": "jane@example.com",
"person": {
"first_name": "Jane",
"last_name": "Doe",
"company": "Acme Inc",
"job_role": "Head of Product",
"city": "San Francisco",
"socials": {
"linkedin": "linkedin.com/in/janedoe"
}
},
"credits": 1000
}

Layer the checks

Layer the checks: corporate domain match first (cheap, catches most), then identity resolution for the ambiguous cases, personal addresses claiming employment, or corporate addresses where you need the person's actual role. A resolved profile whose company and title match the claim is strong evidence; a mismatch triggers your manual-proof fallback.

Badges that mean something

Verification changes community quality in visible ways: employer badges mean something, B2B-only spaces stay B2B, and employee discounts go to employees. Re-verify on a schedule for anything ongoing, people change jobs, and last year's verified employee may be this year's competitor with a grudge and a login.

More email identity use cases

View all
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'