Find a person's professional email

You are wiring up the agntdata "Lead APIs" API to use this endpoint: Find a person's professional email.

1. CONNECT over MCP (preferred). Add the superagnt MCP server, then let the client
   run OAuth on first tool call — no token to paste:
     claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
     claude mcp login superagnt
   MCP endpoint: https://mcp.superagnt.com/mcp
   After connecting, the tool you want is named exactly:
     data_agnt_people_email_finder
   Call agnt_tools_search or agnt_tools_list_enabled to confirm it is available.

2. REST fallback (if you are not using MCP):
     POST https://api.agntdata.dev/people/email-finder
     Header: Authorization: Bearer <YOUR_AGNTDATA_API_KEY>
   Required parameters:
    - (none)
   Optional parameters:
    - first_name (string, optional) — Person's first name. Pair with `last_name` (or use `full_name` instead).
    - last_name (string, optional) — Person's last name. Pair with `first_name`.
    - full_name (string, optional) — Person's full name — alternative to `first_name` + `last_name`.
    - domain (string, optional) — Company root domain (e.g. "tesla.com"). Strongest company signal.
    - company (string, optional) — Company name (alias of `company_name`). Use when domain is unknown.
    - company_name (string, optional) — Company name (alias of `company`).
    - max_cost_cents (number, optional)

3. COST & KEY. This endpoint is priced per call in credits, and each successful response reports its own cost in its meta.costCents field. Only successful calls are charged.
   Get an agntdata API key at https://app.agntdata.dev.

4. TEST. Connect the server (or set the key), discover the tool
   (data_agnt_people_email_finder), run one minimal call with just the required parameters,
   and report back the shape of the JSON response (top-level fields).

Reference (machine-readable variant): https://superagnt.com/docs/apis/lead/agnt/endpoints/people_email_finder.md

{
  "name": "people_email_finder",
  "description": "Find a verified professional email for a person at a company. Identifier fields are at the TOP LEVEL of the body (NOT inside an `identifiers` object): `first_name` + `last_name` (or `full_name`) plus `domain` (or `company` / `company_name`). LinkedIn URL/handle is not currently supported here — if that is all you have, call `/people/enrich` first with `identifiers.linkedin_url` to resolve name + domain, then call this endpoint. agntdata waterfalls cheapest-first across providers until an email is returned (or your `max_cost_cents` budget is exhausted). If you already know the email and want to look up other fields, use `/people/enrich` instead with `identifiers.email`.",
  "parameters": {
    "type": "object",
    "properties": {
      "first_name": {
        "type": "string",
        "minLength": 1,
        "description": "Person's first name. Pair with `last_name` (or use `full_name` instead)."
      },
      "last_name": {
        "type": "string",
        "minLength": 1,
        "description": "Person's last name. Pair with `first_name`."
      },
      "full_name": {
        "type": "string",
        "minLength": 1,
        "description": "Person's full name — alternative to `first_name` + `last_name`."
      },
      "domain": {
        "type": "string",
        "minLength": 1,
        "description": "Company root domain (e.g. \"tesla.com\"). Strongest company signal."
      },
      "company": {
        "type": "string",
        "minLength": 1,
        "description": "Company name (alias of `company_name`). Use when domain is unknown."
      },
      "company_name": {
        "type": "string",
        "minLength": 1,
        "description": "Company name (alias of `company`)."
      },
      "max_cost_cents": {
        "type": "number",
        "minimum": 0
      }
    },
    "required": []
  }
}