companyenrich_people_lookup $0.06125 per call

Reverse email lookup — who is behind this address. Looks up a person by email address — resolves the company from the email domain first, then matches the person by email local-part patterns (CompanyEnrich · People & contact data)

For AI agents: call companyenrich_people_lookup
POST https://toll402.dev/v1/p/companyenrich.people.lookup
{
 "email": "patrick@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": {
  "email": {
   "type": "string",
   "description": "a work email address; free-mail domains will not resolve to a company",
   "examples": [
    "patrick@stripe.com"
   ]
  }
 },
 "additionalProperties": true,
 "required": [
  "email"
 ],
 "description": "READ THE MECHANISM BEFORE TRUSTING THE ANSWER. This is not a mailbox lookup — the provider resolves the employer from the domain and then guesses which employee the local part refers to, from that company's address patterns. Verified live 2026-08-20: `patrick@stripe.com` returned a Stripe employee named Patrick, but NOT the Patrick that address belongs to. Treat the result as a candidate, and conf"
}

MCP

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

All tools · OpenAPI