Use case, Domain email search

Domain email search API for your agent. One call per domain.

Send a company domain. Read email address and full name back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot for Domain email search API - https://looot.ai/use-cases/domain-email-search/skill.md

The short answer

The short answer

Domain email search API for an agent: it sends a company domain to a catalog endpoint and reads email address, full name and job title back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.

  • Email address
  • Full name
  • Job title and department
  • Confidence score
  • Email pattern

The job

What the Domain email search API gives your agent

Sometimes you have a company and no names. A domain search starts from the website address and returns the people and mailboxes found for it, often with a job title and the pattern the company uses for addresses. Your agent turns one domain into a list of contacts to sort and verify.

It takes a different input from the email finder, which needs a full name plus the domain, and from the company email format page, which returns only the pattern. On looot the job id is people.domain.search. Hunter and Tomba return named people, Icypeas returns role mailboxes such as contact@ and support@, and QuickEnrich lists contacts from the company website address.

You give

a company domain

example.com

You get

  • Email address
  • Full name
  • Job title and department
  • Confidence score
  • Email pattern

Providers, cheapest first

What actually differs between providers

Today the price runs from $0.00245 to $0.0190 across 4 endpoints. The dearest costs about 7.8 times the cheapest. Price is only one difference. Each entry below says what that endpoint takes or returns that the others do not.

Sample calls

The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

Request
{"endpointId":"hunter-domain-search-get","input":{"domain":"example.com","department":"sales,marketing","limit":10},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: filters by seniority, department and job titles, and returns each email with a confidence score, plus the domain's pattern and accept-all flag

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one domain.
  • 1 step across 4 providers.
  • Runs on demand, whenever you ask.
Prompt: Domain email search API
Use looot to list the work email addresses found at example.com, with name, job title, department and confidence, sales and marketing first, and show me the cost before you fetch a second page. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot for Domain email search API - https://looot.ai/use-cases/domain-email-search/skill.md

Before you start

Settle these before the first run

  • Filter before the first run. Hunter takes seniority, department and job titles, and Tomba takes department and country, so a sales list does not pay for the whole company.
  • Check how each endpoint bills. Hunter, Icypeas and QuickEnrich bill per result and Tomba per call, so set a limit on a large company.
  • Verify before you send. A found address may have stopped working, so run the list through the email verification API first.
  • Icypeas answers later. Its search runs in the background, and your agent reads the addresses with a second call when it is done.

FAQ

Questions people ask

Send the domain to a domain search endpoint. Your agent gets back the addresses the provider has found, with names and job titles where it has them. Add a department or seniority filter to keep the list short.

Hunter's domain search is one of the endpoints on this page, billed through your looot key. Tomba, Icypeas and QuickEnrich answer the same job, so your agent can try a second provider when the first finds few people.

A domain search starts from the company and lists who it finds. An email finder starts from one person's name and the domain and returns that person's address. Use the email finder page when you already have the names.

Hunter returns the pattern with the results, for example first.last. For the pattern alone, the company email format page compares the endpoints built for it.

Providers list addresses they have seen or can confirm for that domain. A small or new company, or one that publishes few addresses, can return a short list. Try a second provider, or search for people by role and find each email by name.

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

No. looot bills per call, and nothing runs while your agent is idle.
For agents
use case
Domain email search API
run
domain
schedule
on demand
step
Search the domain: hunter tomba icypeas quickenrich
setup
https://looot.ai/use-cases/domain-email-search/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04
markdown /use-cases/domain-email-search.md

Try Domain email search with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.

Start your workspace See agent recipes