# Company email format finder: the pattern a domain uses, so a name becomes an address

Give your agent a company domain and get back the address pattern the company uses, such as first.last or f.last, with how confident the tool is in it. Two tools answer through 鹦鹉AI, each at its own rate. A pattern is a rule, not a mailbox: it tells you how to write an address, and the verify page tells you whether that address exists.

## What is the best way to ask 鹦鹉AI?

Setup line (paste into any agent): `set up 鹦鹉AI — https://parrot.amorist.cn/llms.txt`

Then ask: "Using 鹦鹉AI, get the email format for these 40 company domains, show me the price per domain for each tool first, then give me a table of domain, pattern, confidence and which tool answered, and leave the pattern blank where nothing came back rather than guessing first.last."

- **Give the domain, not the company name** Both tools take a domain. A name has to be resolved to a domain first, and that is a separate call at the same rate.
- **Ask for the confidence with the pattern** A pattern seen on three addresses is a guess; one seen on three hundred is a rule. The number is the difference.
- **Ask for the price per domain** 鹦鹉AI prints both rates before the call, so forty domains has a worst case before anything runs.
- **Do not let the agent default to first.last** A model asked for a format will offer the commonest one. Say that an empty answer stays empty, then verify before sending.

## Why go through 鹦鹉AI

- **No subscription, no seats** Charged per call. No card, no minimum; top up the prepaid balance.
- **Switch by changing a word** Another tool is a different word in the prompt, not a new integration.

Endpoints:

- `thecompaniesapi.companies.email_pattern` — A company's email address patterns by domain (companies): https://parrot.amorist.cn/catalog/companies
- `tomba.companies.email_pattern` — A company's email address patterns by domain (companies): https://parrot.amorist.cn/catalog/companies
- `zerobounce.companies.email_pattern` — Find a company's email address patterns (companies): https://parrot.amorist.cn/catalog/companies

## What people actually struggle with

This is a thin corpus honestly reported: of the ~180 Reddit and X posts read in August 2026 about twenty were on the job, and nine promotional clusters, one in bold Unicode from two accounts, were excluded. Nobody complains about the pattern step itself; they complain about what happens after it.

**The pattern is easy, which cuts both ways**

> "My work email follows a predictable format, so I surmise it's not hard to guess from my name." (r/recruitinghell, 2,112 points: https://www.reddit.com/r/recruitinghell/comments/1r7fc9m/)

What this page can do about it: That predictability is the whole reason a pattern call works, and it is why the call is cheap: most companies follow one rule. The page will not pretend the hard part is here; the hard part is knowing whether the person still has the mailbox.

**The price of the tools, or the price of your evening**

> "You either pay thousands for tools like ZoomInfo/Apollo or you spend hours manually scraping LinkedIn and hoping a generic email format works." (r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1t11un9/)

What this page can do about it: Neither, is the honest answer. A pattern lookup is under one credit per domain, billed from a prepaid balance with no seat and no contract, and the agent can chain it to a verify call so the guess is checked before it is sent.

**Everyone is guessing from the same data**

> "Out of 100 people I actually wanted, maybe one address worth sending to." (X: https://x.com/i/status/2092909603566837762)

What this page can do about it: A pattern will not raise that number on its own. What it changes is the cost of trying: a probable address for everyone on the list for a few credits, then verification to keep the ones that exist. The list itself is still your job.

**Fatigue with the usual databases**

> "I'm increasingly skeptical of relying only on Apollo, Hunter and the usual databases. Everyone is targeting the same people with the same data." (X, 6 likes: https://x.com/i/status/2092548681425694929)

What this page can do about it: A pattern call is not a database of people. It gives you the rule, and you bring the names, which means the addresses you build are for the people you chose rather than the ones every other list already carries.

**Finding the person is the bottleneck, not the address**

> "Scraping Google Maps is easy. Finding the real owner behind each business is the bottleneck." (X, 3 likes: https://x.com/i/status/2092205559961239719)

What this page can do about it: Agreed, and this page does not solve it. Once you have a name and a domain, the pattern makes the address a one line step; the people search and enrichment pages are where the name comes from.

## What actually differs

- A pattern is only as good as the sample behind it. Both tools infer the format from addresses they have seen on the domain, and a domain with three known addresses yields a confident looking pattern that may be wrong for the fourth person. Read the confidence or count the tool returns, and treat anything built on a handful of samples as a hypothesis to verify, not a fact to send to.
- Tomba has been called live through 鹦鹉AI and carries a verified date; The Companies API is documented but not yet verified through 鹦鹉AI, so run one domain before an agent runs a thousand. The 1,300 a month who search for an email format checker are mostly asking whether an address is valid, which is a different call: that is the verify page, and the two calls are meant to run one after the other.

## What is a company email format finder?

It is a call that takes a domain and returns the shape of that company's addresses, learned from addresses already seen on that domain: first.last@, first@, flast@, first_last@ and so on, usually with a count or a confidence behind each. With the pattern and a person's name, an agent can write a probable address for anyone at the company without a per person lookup. It is the cheap first step in an outreach pipeline, and only the first step: a probable address still bounces if the person has left, uses a middle initial or is the one exception, which is why the pattern call is normally followed by a verify call on the address it produced.

## Before you start

**Does the pattern give me a working address?** No. It gives you the rule the company follows, and the address you build from it is probable, not confirmed. Verify it before sending: a bounce from a guessed address costs more in sender reputation than the verify call costs in credits.

**Can I get the pattern from a company name instead of a domain?** Not in one step. Resolve the name to a domain first, which Tomba's suggestions tool does, then ask for the pattern. An agent can chain the two.

**Is guessing addresses from a pattern allowed?** A pattern is public information about how a company names mailboxes, and building an address from it is what every outreach tool does. What you then send, to whom and under which rules is your responsibility, and nothing here changes that.

HTML version: https://parrot.amorist.cn/use-cases/company-email-format