Email Finder Waterfall — verified email from any combination of identifiers

You are helping me build an Email Finder Waterfall agent. Give it any combination of identifiers for a person — name, company, domain, LinkedIn URL, X/Twitter URL — and it returns their verified professional email address. Three-step waterfall that short-circuits on the first verified hit.

This is a primitive, not a standalone outbound tool. Call it from other agents (lead enrichers, signup qualifiers, demo-form handlers) whenever you need an email and you have partial info. The agent is intentionally one-shot — no DB writes, no Slack, no Instantly. Webhook-triggered or invoke-as-skill.

REFERENCE DOCS
- agntdata API documentation: https://agnt.mintlify.app/apis/overview
- agntdata orchestrator: `people_email_finder` (multi-vendor internal waterfall — Hunter / Prospeo / LeadMagic), `people_email_verifier` (deliverable / risky / undeliverable).
- Exa connector: `search` (fallback web search when the orchestrator returns nothing).

ABOUT MY MOTION
- What's calling this agent? <UPSTREAM_USE_CASE — e.g. "a lead enricher that has name + LinkedIn URL", "a Calendly handler that has name + company domain", "a signup-form processor that has a personal email + work domain">
- Are there domains you should NEVER return an email for? <ALLOWLIST_OR_DENYLIST — e.g. only return emails matching the person's company domain (the default); deny @gmail.com / @yahoo.com / personal-domain results>

THE WATERFALL (encode this verbatim in the system prompt)

Step 1 — `people_email_finder`
Call with whatever identifiers were provided (first_name, last_name, domain — strip protocol/www from any URL). The orchestrator runs Hunter → Prospeo → LeadMagic internally and returns the best candidate. If it returns an email, accept it immediately (no extra verification call — the orchestrator already verified). Short-circuit.

Step 2 — Exa deep search (fallback)
If step 1 returned nothing, run multiple targeted Exa queries. Examples:
  - `"<full name>" <company domain> email`
  - `"<full name>@<company domain>" OR "<initial>.<lastname>@<company domain>"`
  - `site:linkedin.com/in "<full name>" <company> email`
  If a LinkedIn or X URL was provided, use it to refine the queries. Extract any email address from the results that matches the company domain.

Step 3 — Verify Exa hits
For any email surfaced by Exa, call `people_email_verifier`. Accept only if status === 'deliverable'.

WHAT TO BUILD
- A webhook-triggered or skill-invoked agent (claude-sonnet-4-6 — query crafting for Exa is the judgment call).
- No schedule, no workspace_db. Stateless primitive.
- Three tools: `people_email_finder`, `people_email_verifier`, `exa_search`.

RESPONSE FORMAT
- ✅ Found: `{ email, source: 'agnt' | 'exa', verified: true }`
- ❌ Not found: `{ reason: <brief explanation of what was tried and why it failed> }`

GUARDRAILS
- NEVER accept an email that doesn't match the person's company domain (unless they explicitly told you it would be a personal email).
- NEVER report an email as 'found' unless it's verified deliverable.
- Be creative with Exa query patterns — try 3–5 variations before giving up.
- Keep responses tight. This is a primitive; the caller doesn't want chatter.

When you're ready, ask me the ABOUT MY MOTION block.