email-finder

Find and verify work emails for prospects from a name and company — one call per lookup, and it never reads your inbox.

Find a person’s work email from their name and company, verify any address before sending, or list the known addresses on a domain — three endpoints, one key. Lookups run as an orchestrated waterfall across multiple email data providers server-side: the agent makes one call and gets the best verified answer, with deliverability status attached. Built for outbound agents that need send-ready addresses, list-cleaning jobs that verify before a campaign, and enrichment flows that finish a lead record with a working email.

Alternative install: the scoped MCP server

If this client speaks MCP, you can connect the Email Finder facet server instead of using this skill's curl calls — the same endpoints below as native MCP tools with structured parameters and OAuth sign-in, scoped to this capability:

text

https://mcp.superagnt.com/mcp/email-finder

That URL publishes full OAuth discovery: an MCP-capable client needs the URL and nothing else (approve once in the browser). On clients that hold a bearer instead, add it as an Authorization: Bearer header. Per-client setup lines: https://www.superagnt.com/install?facet=email-finder

This skill document stays fully usable on curl-only environments — everything below works with just the API key.

Authentication

Get an API key from the superagnt app and export it as SUPERAGNT_API_KEY. Every request sends it as a Bearer token:

text

Authorization: Bearer $SUPERAGNT_API_KEY

If the variable is not set, ask the user for their key or point them at https://superagnt.com/r/ch-email-finder-key.

Verify the install (do this first)

One call proves the key, the credit balance, and this source end to end:

bash

curl -s https://api.superagnt.com/v1/credits \
  -H 'Authorization: Bearer $SUPERAGNT_API_KEY'

A JSON result means you are live. A 401 means the key is wrong or missing; a 402 means the workspace is out of credits — the superagnt app shows both.

Base URL

text

https://api.superagnt.com/v1/data/agnt

Available Endpoints

Method	Path	Summary
POST	/people/email-finder	Find a person's professional email
POST	/people/email-verifier	Verify a professional email
POST	/companies/domain-emails	List a domain's emails

Tool Schemas

The following JSON defines every operation with its parameters. Each tool maps to an API endpoint under the base URL.

json

[
  {
    "name": "superagnt_agnt_people_email_finder",
    "description": "Find a person's professional email",
    "method": "POST",
    "path": "/people/email-finder",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEmailFinderRequest"
    }
  },
  {
    "name": "superagnt_agnt_people_email_verifier",
    "description": "Verify a professional email",
    "method": "POST",
    "path": "/people/email-verifier",
    "parameters": {
      "$ref": "#/components/schemas/PeopleEmailVerifierRequest"
    }
  },
  {
    "name": "superagnt_agnt_companies_domain_emails",
    "description": "List a domain's emails",
    "method": "POST",
    "path": "/companies/domain-emails",
    "parameters": {
      "$ref": "#/components/schemas/CompaniesDomainEmailsRequest"
    }
  }
]

Example

bash

curl -X POST 'https://api.superagnt.com/v1/data/agnt/people/email-finder' \
  -H 'Authorization: Bearer $SUPERAGNT_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"...": "see tool schemas below"}'

Use Cases

Scope

This skill covers Email Finder only — the endpoints listed above, nothing else. The same API key also works with superagnt's other data sources and platform tools, but those are separate listings that the user installs or enables themselves; this skill does not add or enable anything beyond what is documented here. The public catalog is at https://api.superagnt.com/v1/platforms.

Links

• Documentation
• superagnt app / API keys
• This listing