Find the verified professional email address of a person from name and employer domain.

What we did not test, and why

Not specified in this bundle.

Legal preflight, verdict per tool

Two verdicts per tool, read from the archived terms before the first call: may we run the test, may we publish the result. A tool that was not run keeps its recorded reason. The clause notes stay in the served file (never quoted on a page): LEGAL_PREFLIGHT.json.

Right of reply

Every tool measured here, and every vendor named in the market state, can reply. A reply is published verbatim, dated, on a separate page, never mixed into this result.

• dropcontact: notified 3 Sep 2026, window closes 17 Sep 2026, no reply received
• lusha: notified 3 Sep 2026, window closes 17 Sep 2026, no reply received

How to reproduce

gladiator reproduce runs/EMAILFIND-001

Canonical JSON: latest result of the category, this run. Evidence path in the public repository: runs/EMAILFIND-001.

Reproduction files served byte-identical to the repository: events.ndjson (hash-chained journal), PROTOCOL.lock, contest.yaml, LEGAL_PREFLIGHT.json; schema result.v1.json. Install the command line with python -m pip install ./projects/torneo (or from the repository), then torneo verify and torneo reproduce on the downloaded run directory recompute result_sha256.

Machine surfaces (MCP server, canonical JSON, llms.txt): For agents.

What this does not prove

Errata

Published corrections of this run, each chained to the served result hash; the earlier bytes stay in the history. Full record: ERRATA.md.

• ERR-001, 4 Sep 2026: erratum ERR-001: conflicts served empty while devlo is a customer of both measured tools (Dropcontact, Lusha; run paid from devlo prepaid credits) and runner carried internal lane jargon; amendment A6 (contest.yaml frozen). Estimates, intervals, status unchanged. (served result 08fdd2ce replaced by 6c842104)

• Population limited to employer-published emails: absolute rates are optimistic bounds; tool-to-tool comparison remains valid (same frozen set for all).
• Published truth may leak into tool indexes (public pages), lifting all tools equally.
• Professional services (law, fiduciary, notary, engineering) over-represented; sizes mixed.
• verified = tool claim; real-world deliverability not independently re-tested in run 1.
• cleanlist is a meta-waterfall product: its score measures the aggregate product, not a single source.
• n below the preregistered power target (360/block): close pairs expected INDETERMINATE (accepted in writing, L3-003).
• Costs are credit estimates at public per-credit prices (prices.json); subscriptions prorated there.
• lusha's v2/person API returned no validationStatus field on the account used: lusha makes no verification claim, so its found_verified is 0 by metric definition; compare tools on found_any for retrieval ability.
• Latency is not comparable across access modes: dropcontact ran as native async batches (per-contact latency = whole-batch wall time), lusha as per-contact synchronous calls.
• Precision insufficient under the frozen protocol: no rank published.

What no TORNEO result can tell you, for every category: Limits.

Conflicts and funding

Run by devlo (agent-operated), funding: devlo own funds; no vendor money. Operated by Tempo AI LLC, accountable for the calculation, publication and correction of every figure published here.

Conflicts declared in this bundle:

• dropcontact: devlo is a customer of Dropcontact and this run was paid from devlo's existing prepaid credits; devlo is a user of the tool, not a vendor; same conditions and credits for every arm, journaled (CONFLICT_REGISTER.json: USER_OF_TOOLS)
• lusha: devlo is a customer of Lusha and this run was paid from devlo's existing prepaid credits; devlo is a user of the tool, not a vendor; same conditions and credits for every arm, journaled (CONFLICT_REGISTER.json: USER_OF_TOOLS)