findymail_search_name $0.02475 per call

Find a work email from a name and company domain. Find someone's verified professional email from their full name and their company's domain (Findymail · People & contact data)

For AI agents: call findymail_search_name
POST https://toll402.dev/v1/p/findymail.search.name
{
 "name": "Patrick Collison",
 "domain": "stripe.com"
}
Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server: npx -y toll402-mcp · remote https://toll402.dev/mcp.

Input schema

{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "the person's full name",
   "examples": [
    "Patrick Collison"
   ]
  },
  "domain": {
   "type": "string",
   "description": "the company domain, no protocol or www",
   "examples": [
    "stripe.com"
   ]
  },
  "webhook_url": {
   "type": "string",
   "description": "if set, the result is POSTed here instead of being awaited inline"
  }
 },
 "additionalProperties": true,
 "required": [
  "name",
  "domain"
 ],
 "description": "returns {contact: {...}} on a hit and a null/empty contact on a miss; a miss is NOT charged. The contact object always carries company, job_title, linkedin_url and city/region/country keys, but they come back empty or null when Findymail has no profile data for the person — only `email`, `name` and `domain` are dependable. Note the returned `domain` can be an alias of the one you asked for (stripe"
}

MCP

{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}

All tools · OpenAPI