Enrichment

Enrichment starts from someone you chose. Nothing has to have happened: you name a company or a person, and mySDR returns the people who decide there, their profile, a work email, a phone number, or the facts about the company. That is the difference with Signals, which start from a buying moment and tell you who just did something.

What you have, what you get#

• A company, or a list of up to 25, and you want the people who decide there → Decision makers: search_people with companies, on every key.
• A list of companies by name, industry, size, place, technology, or like a company you know → Decision makers: lookup_company (free), Search Companies (search_companies), and companies using a technology.
• A LinkedIn profile, and you want the full profile and a work email → People enrichment: enrich_people.
• A name and a company domain, but no LinkedIn profile, and you want a work email → People enrichment: enrich_people with people.
• A LinkedIn profile, and you want a phone number → People enrichment: find_phones.
• A work email address, and you want the person and company behind it → People enrichment: reverse_email_lookup.
• A personal email address (Gmail, Outlook …), and you want the person behind it → People enrichment: reverse_email_lookup.
• A company, and you want headcount, locations, funding and open roles → Company enrichment: enrich_companies.
• A company, and you want its tech stack → Company enrichment: get_tech_stack.

Who can use what#

• Every key and every assistant: Search People (also the people at a list of companies), Enrich People (also a work email from a name), Find Phone, Reverse Email Lookup, Search Companies (search_companies), Enrich Companies (enrich_companies) and the technology data (a tech stack, companies using a technology). These are open on every plan with API access.

A valid key on an API that is closed for your organization answers 403 api_not_enabled, with what the key can do instead.

How a lookup is charged#

You pay for what comes back, never for a miss: 1 credit per lead from Search People (at least 3 credits for a search that finds someone), 0.6 credits per profile, 0.6 credits more per work email found (also from a name, without a profile), 10 credits per phone number found (once per person), 1 credit per person found behind an email, 1 credit per company enriched and 3 credits per tech stack. Every paid call takes max_credits: it stops before the next row would pass the cap. The whole table is Credits & costs.

How a work email is checked#

A work email is built from the name and the company domain and checked over SMTP; when the first source finds nothing, a second source looks. Every address comes with email_status: verified (the mail server accepted it), catch_all (the domain accepts any address, so the mailbox itself cannot be confirmed), unverifiable (the check could not confirm it) or not_found, and pending while the second source still looks. person.email adds deliverable, catch_all, a quality_score when the source gives one, and checked_at: when the address was checked, the time of the call or, for an address the second source found earlier and that is reused, when it found it (at most 90 days ago). How many addresses are found differs per country and per company. Measured on 27 October 2026, Enrich People found a work email for 123 of 139 people (88%) in seven European countries, 64 verified and 59 catch-all: Work emails per country. Test it on people whose email you know with your free credits: Evaluate mySDR.

Save what you keep#

A result is not in the user’s tables until your agent saves it: save_leads (POST /tables/leads) for people and save_companies (POST /tables/companies) for companies, each with a note why. An enriched profile carries save_input: the fields save_leads takes, with the work email and its status, so the address lands on the row. See Tables and your process.

A typical path#

1. "Find the CFO of Acme Analytics in Belgium." → search_people with companies, current_job_titles and locations.
2. "Get me their work email." → enrich_people with include_email, only for the person you keep.
3. "Save them to my Leads with a note." → save_leads, and the answer ends with the link to the Leads table.