Email Finder API

السجل الرسمي الإنتاجية

Find email addresses from name and company domain. x402 paid.

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (sse)
Claude Code
claude mcp add --transport sse email-finder-api 'https://email-finder.api.klymax402.com/mcp'
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "email-finder-api": {
            "type": "sse",
            "url": "https://email-finder.api.klymax402.com/mcp"
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Email Finder API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Email Finder API

Find professional email addresses from name + company domain. Tests 15+ patterns against MX records with confidence scoring. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "email-finder": {
      "url": "https://email-finder.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl "https://email-finder.api.klymax402.com/api/find?domain=...&firstName=...&lastName=..."
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
email_find_by_nameGET/api/find$0.012Find a person's email from their name and company domain
email_find_by_namePOST/api/find$0.012Find a person's email from their name and company domain (POST variant)
email_find_by_name

Search for people/contacts matching criteria and find their professional email address from name and company domain. Alternative to Apollo people-search at 4x lower cost. Returns the most likely email with confidence score after testing 15+ patterns against MX records.

Parameters

NameTypeRequiredDescription
domainstringyesCompany domain (e.g. company.com)
firstNamestringyesPerson's first name (e.g. John)
lastNamestringyesPerson's last name (e.g. Doe)

Example response:

{"email":"john.doe@stripe.com","confidence":92,"pattern":"first.last","allCandidates":[{"email":"john.doe@stripe.com","score":92},{"email":"jdoe@stripe.com","score":75},{"email":"john@stripe.com","score":60}],"domain":"stripe.com","mxValid":true}

When to use: sales outreach, cold emailing, or building prospect contact lists. Essential for searching for people/contacts and finding decision-maker emails when you only know their name and company. Drop-in replacement for Apollo people search.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), person data from email (use person_enrich_from_email).

email_find_by_name

Search for people/contacts matching criteria and find their professional email address from name and company domain. Alternative to Apollo people-search at 4x lower cost. Returns the most likely email with confidence score after testing 15+ patterns against MX records. POST variant of email_find_by_name -- same params passed as JSON body instead of query string.

Parameters

NameTypeRequiredDescription
domainstringyesCompany domain (e.g. company.com)
firstNamestringyesPerson's first name (e.g. John)
lastNamestringyesPerson's last name (e.g. Doe)

Example response:

{"email":"john.doe@stripe.com","confidence":92,"pattern":"first.last","allCandidates":[{"email":"john.doe@stripe.com","score":92},{"email":"jdoe@stripe.com","score":75},{"email":"john@stripe.com","score":60}],"domain":"stripe.com","mxValid":true}

When to use: sales outreach, cold emailing, or building prospect contact lists. Essential for searching for people/contacts and finding decision-maker emails when you only know their name and company. Drop-in replacement for Apollo people search.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), person data from email (use person_enrich_from_email).

Example agent prompts

  • "Search for people/contacts matching criteria and find their professional email address from name and company domain"
  • "Search for people/contacts matching criteria and find their professional email address from name and company domain"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

الأسئلة الشائعة

ما هو Email Finder API؟

Find email addresses from name and company domain. x402 paid.

كيف أثبّت Email Finder API؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport sse email-finder-api 'https://email-finder.api.klymax402.com/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Email Finder API إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل Email Finder API مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Email Finder API؟

ينشره Br0ski777. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.