← Blog

Best way seriesNovember 16, 2026

The best way to find a work email with AI

Give your agent a LinkedIn URL or a name and company, call vaaya/onefind-deep (charged only when a lookup returns data), then verify the address for 0.089¢.

The best way to find a work email with an AI agent is to give it one identifier for the person, a LinkedIn URL or a name and company, and have it call vaaya/onefind-deep. That single call tries ContactOut and then Tomba, and you are charged only for lookups that return data. Before anything is sent, the agent runs the address through tomba/email-verifier for 0.089¢.

This post starts once you know who the person is. To choose the person, read how to find the right people at a company.

What "best" means for this job

  • Cost per found address. The price of a call matters less than what you pay when it finds nothing.
  • A work address. Some finders also return personal addresses, which outreach should leave alone.
  • Deliverability. A found address is a candidate until a verifier has checked it.

The finders and verifiers in the catalog

Prices are as listed on 16 November 2026. The catalog has current prices.

Tool What it returns Price per call When to pick it
vaaya/onefind-deep A row per person with email, phone, sources and hops Holds budgetCents (10 to 500), or 2¢ plus 16¢ a row. Settles at the price of the lookups that returned data The default: one identifier in, both finders tried
contactout/linkedin-contacts Work and personal emails from a LinkedIn URL 10¢, or 30¢ with include_phone: true You want everything on file, or a phone
tomba/email-finder The most likely address for a name and domain, with a confidence score 4¢ No LinkedIn URL, or the default came back empty
tomba/linkedin-finder The email behind a LinkedIn URL 0.089¢ A second source for a URL
icypeas/email-search Addresses with a certainty grade, from a name and domain (async) 4¢, plus 1¢ per icypeas/result read After a Tomba miss
tomba/email-verifier deliverable, undeliverable or risky 0.089¢ Before any send
icypeas/email-verification An SMTP-level check on separate infrastructure (async) 0.19¢, plus 1¢ per icypeas/result read A second opinion on risky
contactout/email-verify A deliverability check 2¢ An alternate verifier

The default path

Start with vaaya/onefind-deep and pass the identifier in rows. For a LinkedIn URL it calls contactout/linkedin-contacts, then tomba/linkedin-finder only if ContactOut comes back empty. A name and company string is first matched to a profile with a 1¢ people search. The 10¢ lookup goes first in Vaaya's routing notes: a ContactOut miss costs nothing.

What a miss costs, as the catalog and the routing notes state it:

  • vaaya/onefind-deep is charged on fill. The job holds your budget and settles at its own price for each lookup that returned data: 10¢ for ContactOut, 4 to 5¢ for Tomba, 1¢ for the profile search. Empty lookups cost nothing, and the unused hold returns to your balance.
  • contactout/linkedin-contacts, called directly, is free on a miss.
  • tomba/email-finder and icypeas/email-search are listed at a flat 4¢. Their descriptions say the vendor bills upstream only when an email is found. Nothing in the catalog promises the Vaaya price back on a miss, so budget 4¢ an attempt, plus 1¢ per icypeas/result read.
  • The routing notes name one Tomba action that bills on a miss: tomba/enrich, which goes from an email to a person.

Step up from the default in three cases.

  1. The row comes back with email: null. That is a real answer from the vendors the job asked, so do not repeat those lookups by hand. It did not try a search by name and domain: tomba/email-finder, then icypeas/email-search if Tomba misses.
  2. You need a phone number, or every address on file. Call contactout/linkedin-contacts directly.
  3. Every finder misses. tomba/domain-search (0.089¢) lists the known addresses at the company and its email pattern. An address built from a pattern stays a guess until a verifier accepts it.

One lookup, priced

This is arithmetic at listed prices on 16 November 2026, not a record of a run.

You hold a LinkedIn URL for one person. The agent starts the job:

{
  "service": "vaaya",
  "action": "onefind-deep",
  "params": {
    "rows": ["https://www.linkedin.com/in/jane-doe-example"],
    "budgetCents": 16
  },
  "max_cost_cents": 16
}

The call returns a job_id. The agent polls result with that id until the row arrives. Polling is free, and it should never restart the job to check on it. Then it verifies the address:

{
  "service": "tomba",
  "action": "email-verifier",
  "params": { "email": "jane.doe@example.com" },
  "max_cost_cents": 2
}
  • ContactOut returned the data: 10¢ + 0.089¢ = 10.089¢.
  • ContactOut was empty and Tomba returned it: 5¢ + 0.089¢ = 5.089¢.
  • Neither vendor had the person: 0¢, with nothing to verify.

For 25 URLs in one rows call, budget 25 × 16¢ = $4.00. The lookups settle at no more than 25 × 10¢ = $2.50, and 25 verifications add about 2¢, so the ceiling is about $2.52.

Verify before you send

Verify every address before it counts as usable, however it was found.

  • tomba/email-verifier is the primary check in Vaaya's routing notes. Send to deliverable. Drop or re-research undeliverable.
  • risky is a judgment call. Webmail and catch-all domains often land there. When the send matters, cross-check with icypeas/email-verification.
  • contactout/email-verify is an equivalent alternate at 2¢.

A verifier tests the mailbox. It cannot confirm that you matched the right person, so check the name, title and company in the row.

Use it responsibly

Keep the list to work addresses. contactout/linkedin-contacts returns personal addresses as well, so read work_email and leave the rest out. Write only to people with a plausible reason to hear from you, and say what it is. Keep a suppression list and check it before every send. Anyone who opts out goes on it.

How to run it

Connect your agent over MCP, the API or the SDK, then ask in plain English:

Find the work email for the person at this LinkedIn URL: [URL]. Use Vaaya and ask consult for the plan and prices first. Spend at most 20¢. Verify the address and tell me which vendor it came from. Do not send anything.

The agent can ask Vaaya's consult tool to plan the calls and quote each price before it commits. Every call carries max_cost_cents, and a call priced above that ceiling is refused without a charge. tomba/email-verifier is charged 0.089¢, but Vaaya first checks and holds 2¢, so its max_cost_cents must be at least 2.

What to check, and where this falls short

  • Read sources and hops on the row: which vendor filled the address, and what each lookup cost.
  • Compare the address's domain with the company's. A row can carry a personal address when no work one is on file, and tomba/linkedin-finder can return a personal-domain or previous-company address.
  • In rows, write the company as a name. A string that contains a domain is read as a company, and OneFind resolves people only.
  • Batch rows the budget could not cover come back marked over budget. Raise budgetCents or send fewer rows.
  • No finder has everyone. When every rung misses, leave the field empty.

Why this suits a pay-per-call wallet

Email lookups arrive in bursts: forty names after an event, then none for two weeks. The job touches three vendors, and a wallet lets your agent reach all of them from one balance, paying only for fills on the default path. Give the agent's key a weekly limit and restrict it to the Data category (see spending controls), and a retry loop stops at the limit. The smallest pack on the pricing page is $14, which covers 138 found and verified addresses at 10.089¢ each.

Questions

How much does it cost to find a work email with an AI agent?

Through vaaya/onefind-deep you pay for the vendor lookups that return data: 10¢ when ContactOut supplies it and 5¢ when Tomba's LinkedIn finder does, at prices listed on 16 November 2026. Verifying the address with tomba/email-verifier adds 0.089¢.

Do I pay when no email is found?

On vaaya/onefind-deep, no. It is charged on fill, so an empty lookup costs nothing. A direct contactout/linkedin-contacts call is also free on a miss. For direct tomba/email-finder and icypeas/email-search calls the catalog lists a flat 4¢ and does not promise a free miss, so budget the listed price for each attempt.

Should I verify an email that a finder returned?

Yes. Verify every address before you treat it as usable, however it was found. tomba/email-verifier costs 0.089¢ and returns deliverable, undeliverable or risky. A verifier checks the mailbox. It does not confirm that you matched the right person.

Can an agent find an email from only a name and a company?

Yes. Pass the name and company name as one string to vaaya/onefind-deep, which first resolves the person to a profile with a 1¢ people search. If you know the company domain, tomba/email-finder takes a name and domain for 4¢.

Find your first work email

Connect your agent to Vaaya, put a limit on its key and hand it one LinkedIn URL.

Connect an agent