Loading
A name and a company in. A work address out, or an honest miss.
The most requested job in B2B data, and the one most often done badly. Guessing a pattern from a domain produces an address that looks right and bounces, which costs more than not sending at all.
The waterfall asks your cheapest configured provider first and stops the moment one returns a verified result. Pattern inference is a last resort, and anything derived that way is labelled as derived rather than found.
Resolve the company to a canonical domain before asking anyone. Most failed lookups are failed company matches wearing a disguise.
Your configured providers are queried cheapest first. The expensive one is only reached when the cheap ones have genuinely failed.
A found address is checked for deliverability in the same call. An unverified address never leaves the system labelled as verified.
Which provider answered, whether it was cached, and whether the result was found or inferred.
ProvidersFans out to whichever providers you have configured — the usual candidates are the large B2B databases and the email-specific finders. You hold those accounts; we only orchestrate them.
Every one of these is a genuine constraint of the underlying data, not a gap we intend to close later. Anyone claiming otherwise is guessing on your behalf.
Honest limits
The playground shows what this looks like as an agent tool call and as plain HTTP — including what a miss and a refusal return. Illustrative, not live.