Personal Email to Company Resolver
Pricing
from $21.25 / 1,000 email resolveds
Personal Email to Company Resolver
Find the employer behind a Gmail, Outlook, or other free mail signup. One row per address with the person's name, likely employer, employer domain, and a confidence, from the public Gravatar profile, signed GitHub commits, and LinkedIn results. Never contacts the mailbox. Clay ready.
Pricing
from $21.25 / 1,000 email resolveds
Rating
0.0
(0)
Developer
Mamba Labs
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 hours ago
Last modified
Categories
Features
Share
Find the likely employer behind a free mail address. A signup on a Gmail, Outlook, iCloud, or Yahoo address tells you nothing about the company; this actor reads the public signals tied to that address and returns one row with the person's name, the likely employer, its domain where a source names it, and a confidence.
It never sends mail, never probes a mailbox, and never opens LinkedIn. Every signal is public and tied to the exact address.
Rows are flat and snake_case, so they load straight into a spreadsheet, a CRM, or a Clay table.
⨠Features
- Built for product led signups. Free mail addresses in, employers out. About 140 consumer mail domains are recognized; a company address returns its own domain, free.
- Signals tied to the address, strongest first. The public Gravatar profile for the address hash, the GitHub account whose public commits are signed with the address (and its organization's site), and an exact Google search for the address.
- Confirmed on LinkedIn results. Every address with a name goes to Mamba Labs Person LinkedIn URL Resolver in one child run. A current match raises the confidence and adds the profile URL; a former match lowers it.
- A confidence you can filter on.
resolvedneeds 0.75 or more and is the only billed row. - Evidence on every row.
employer_source,evidence_urls, andsources_checkedsay where each answer came from. - Batch input. Up to 300 addresses per run.
đĨ Input
| Field | Type | Description |
|---|---|---|
email | string | One address |
emails | list | Several addresses, one per line, up to 300 |
github_token | secret | Optional, your own free GitHub token, for batches over about 40 addresses |
search_web | string | true (default): one exact Google search when Gravatar and GitHub name no employer |
use_linkedin_resolver | string | true (default): one child run of Person LinkedIn URL Resolver for the addresses with a name, billed at that actor's own price. false skips it |
country | string | Google country code, default us |
max_charge_usd | string | Optional cost cap for the run, passed to the child run too |
Example:
đ¤ Output
One row per address. Every row carries every field; a field that does not apply is null.
| Field | Example | Notes |
|---|---|---|
email, email_domain, email_type | gmail.com, free_mail | free_mail, corporate, invalid |
person_name, name_source | Jane Doe, github | gravatar, github, web_result, email_local_part |
employer_name, employer_domain | Acme, acme.io | The domain only when a source names it |
job_title | The title or headline a source gives | |
employer_source | github | gravatar, github, web_result, linkedin_headline, email_domain |
employer_confidence | 0.93 | 0 to 1 |
match_status | resolved | resolved, weak, name_only, corporate_email, not_found, invalid_email, blocked |
linkedin_url, linkedin_match_status, linkedin_company_match | From Gravatar or the LinkedIn step | |
github_login, github_url, gravatar_url, location | janedoe | |
evidence_urls, sources_checked | Where the answer came from | |
row_status, error_reason | ok | |
billable_events_json | {"email-resolved":1} | What the row was billed as; {} is free |
source, checked_at |
No phone number or street address is returned. There is no field for one.
đ Measured results
Measured on 2026-10-21 over 21 free mail addresses taken from public, signed commits in eight popular open source repositories, plus one made up control address, with no GitHub token:
- 10 of 21 resolved to an employer at 0.75 or more. 9 more returned a name with no employer, and 2 returned nothing.
- 10 of 10 resolved employers match the company the person states on their own public GitHub or Gravatar profile. The LinkedIn step confirmed 2 of the 10 as current; for one more it showed the employer's acquirer instead, which the row reports.
- The control address returned
not_found. - Speed: about 13 s per address without a GitHub token, set by GitHub's limit of 10 searches a minute; a free token makes it about three times faster.
Coverage depends on the audience. These addresses come from developers who sign public commits; a consumer signup list will resolve far fewer.
đĩ Pricing
Pay per event. You pay for an address whose employer was resolved, plus a small start fee per run.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
Email resolved (email-resolved), per address with an employer at 0.75 or more | $0.02500 ($25.00 per 1,000) | $0.02375 ($23.75 per 1,000) | $0.02250 ($22.50 per 1,000) | $0.02125 ($21.25 per 1,000) |
Actor start (apify-actor-start), per run | $0.0005 | $0.0005 | $0.0005 | $0.0005 |
weak,name_only,corporate_email,not_found,invalid_email,blocked, anderrorrows cost nothing.- The LinkedIn step is a second actor. With
use_linkedin_resolveron (the default), one run of Mamba Labs Person LinkedIn URL Resolver starts from your Apify account for the addresses with a name and an employer. Apify bills it at that actor's own price: $0.03500 per person sent to it, found or not, plus $0.0005 per run, on top of this actor's events. Setuse_linkedin_resolvertofalseto skip it. - A run stops at the maximum cost per run you set in Apify, and at
max_charge_usdif you set it. - Free Apify plan: 1.50 USD of evaluation a month, which is 60 resolved emails at the free plan price. Any paid Apify plan removes the cap.
- Apart from the LinkedIn step, the events above are all you pay this actor. Mamba Labs pays the platform costs of your run, Apify proxy traffic included.
đ Usage examples
Console or API. POST https://api.apify.com/v2/acts/mambalabs~personal-email-to-company-resolver/runs with the input above, then read the default dataset.
No LinkedIn step.
Clay. Call the actor from a Clay column with the email column mapped to email. Clay sends every field as a string, which this actor expects. Filter on match_status = resolved.
MCP. The @mambalabsdev/mcp-personal-email-to-company-resolver server exposes the tool resolve_personal_email_employer to AI agents.
â ī¸ Error handling
| Situation | What you get |
|---|---|
| No public signal for the address | One free row, not_found |
| A name but no employer | One free row, name_only |
| An employer below 0.75 | One free row, weak, with the employer and its source |
| GitHub's published rate limit is reached | Later addresses skip GitHub; add a free github_token |
| The LinkedIn step fails | Rows keep their Gravatar and GitHub answers; linkedin_match_status says not_run |
| Anything else | One free error row with the reason |
â ī¸ Limitations and responsible use
- Coverage is highest for people who build or write in public: developers with signed commits, people with a Gravatar profile. Many free mail signups leave no public trace and come back
not_found. See the measured numbers above. - A GitHub or Gravatar company field is what the person wrote, and can be out of date. The LinkedIn step catches a former employer when the LinkedIn result marks it.
- No mailbox is contacted, no SMTP check is made, and LinkedIn is never opened.
- GitHub's Acceptable Use Policies do not allow its users' information to be used for spam, for unsolicited email, or for selling personal information. You are responsible for using GitHub data within those terms.
- You are the data controller under GDPR, CCPA, and applicable privacy laws for the rows you collect. Use the actor on addresses that reached you directly, such as your own signups. The actor keeps no personal data after the run.
𧊠Want other GTM data?
Mamba Labs builds a fleet of enrichment actors that share one flat output convention:
Every actor in the suite takes a domain, a company, or a person and returns flat rows, so they stack in the same table without reshaping anything.
đ Support
Found a bug? Open an issue on the Issues tab. Response time is typically within 48 hours.
âšī¸ Sourcing. Signals come from the public Gravatar API, the public GitHub API, Google result pages read through the Apify Google SERP proxy, and Mamba Labs Person LinkedIn URL Resolver. You are responsible for how you use the output.
Built by Mamba Labs.
