sales-anymailfinder

What this skill does

# Anymail Finder Platform Help

Help the user with Anymail Finder platform questions — from Email Finder (by person, company, decision maker, or LinkedIn URL) through Email Verification, Bulk Email Search, GeoLead Finder, and Domain Email operations. Anymail Finder is a London-based email finder and verification tool (AMF Internet Services Limited, founded 2015) offering a 97%+ delivery guarantee on verified emails, a REST API with no rate limits, and a Chrome Extension for in-workflow lookup.

## Step 1 — Gather context


If `references/learnings.md` exists, read it first for accumulated knowledge.

Ask the user:

1. **What area of Anymail Finder do you need help with?**
   - A) Email Finder by Person — find a verified email from first name + last name + company/domain (1 credit per valid result)
   - B) Email Finder by Company/Domain — find up to 20 email addresses at a company (1 credit)
   - C) Email Finder by Decision Maker — role-based search (ceo, engineering, finance, hr, it, logistics, marketing, operations, buyer, sales) returning name, title, LinkedIn URL, email (2 credits per valid result)
   - D) Email Finder by LinkedIn URL — extract email from a LinkedIn profile URL (1 credit)
   - E) Email Verifier — validate an email address as valid/risky/invalid (0.2 credits)
   - F) Bulk Email Search — process up to 100,000 rows asynchronously via JSON or CSV/Excel upload
   - G) GeoLead Finder — location-based lead discovery
   - H) Chrome Extension — browser-based email finding from any website
   - I) Domain Email Count/Order/Download — count, order, and download all emails at a domain
   - J) API — REST API setup, endpoints, authentication, webhooks
   - K) Account / Billing — plans, pricing, credits
   - L) Something else — describe it

2. **What's your role?**
   - A) Sales / SDR / BDR
   - B) RevOps / Sales ops
   - C) Developer / engineer
   - D) Growth / marketing
   - E) Recruiter / talent acquisition
   - F) Other

3. **What are you trying to accomplish?** (describe your specific goal or question)

**If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

## Step 2 — Route or answer directly

If the request maps to a specialized skill, route:
- Cross-platform enrichment strategy / multi-tool enrichment -> `/sales-enrich`
- Email deliverability / warmup strategy (not Anymail Finder-specific) -> `/sales-deliverability`
- Prospect list building strategy -> `/sales-prospect-list`
- Connecting Anymail Finder to other tools via middleware -> `/sales-integration`
- Hunter.io-specific questions -> `/sales-hunter`
- Apollo-specific questions -> `/sales-apollo`
- Prospeo-specific questions -> `/sales-prospeo`
- Tomba-specific questions -> `/sales-tomba`
- Enrich.so-specific questions -> `/sales-enrichso`
- GetProspect-specific questions -> `/sales-getprospect`
- Minelead-specific questions -> `/sales-minelead`
- Skrapp-specific questions -> `/sales-skrapp`

Otherwise, answer directly from platform knowledge using the reference below.

## Step 3 — Anymail Finder platform reference

**Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

## Step 4 — Actionable guidance

Based on the user's specific question:

1. **Finding a specific person's email by name and company**:
   1. Call `POST /v5.1/search/person.json` with `full_name` and `company_name` or `domain` in the request body, with `Authorization: <your-api-key>` header
   2. Set your HTTP client timeout to at least 180 seconds — real-time searches can take up to 3 minutes as the system checks multiple data sources
   3. Check the response status: `valid` means the email is verified with 97%+ delivery guarantee, `risky` means unverified (returned free but less reliable), `not_found` means no result (also free)
   4. For valid results, use the email directly for outreach — the 97%+ guarantee means very low bounce risk
   5. For risky results, consider running the Email Verifier separately or cross-checking with another tool before outreach
   6. Re-searching the same person within 30 days is free — safe to retry if you need to check again

2. **Finding decision-maker emails by role at a company**:
   1. Call `POST /v5.1/search/decision_maker.json` with `domain` and `category` (one of: ceo, engineering, finance, hr, it, logistics, marketing, operations, buyer, sales)
   2. Note that this costs 2 credits per valid result (double the person search) — budget accordingly for large lists
   3. The response includes name, title, LinkedIn URL, and email — useful for building account maps without knowing specific names
   4. For multiple roles at the same company, make separate requests per category
   5. Combine with the Email Verifier (0.2 credits) if you want additional validation beyond the initial search

3. **Running a bulk email search for a large prospect list**:
   1. Prepare your data as JSON (up to 100,000 rows) or as a CSV/Excel file
   2. Submit via `POST /v5.1/bulk/search.json` (JSON) or `POST /v5.1/bulk/upload.json` (file upload)
   3. Include `x-webhook-url` header if you want to be notified when processing completes
   4. Processing is async — expect approximately 1,000 rows every 5 minutes
   5. Credits are charged only when you download results, not when you submit the job — you can review the output before committing credits
   6. Download results when the job completes and filter by status: prioritize `valid` emails, handle `risky` results with caution

4. **Verifying an existing email list**:
   1. For individual emails: `POST /v5.1/verify.json` with `email_address` — returns valid, risky, or invalid status at 0.2 credits each
   2. Repeated verifications of the same email within 30 days are free
   3. For large lists, use bulk operations to process efficiently
   4. Filter results: use `valid` emails for outreach, flag `risky` for manual review, discard `invalid`
   5. Be aware that catch-all domains may return `risky` status even for valid mailboxes — these domains accept all mail regardless of whether the address exists

## Gotchas

> *Best-effort from research — review these, especially items about credit costs, API behavior, and feature limitations that may have changed since this was written.*

1. **Decision Maker search costs 2x — 2 credits per valid result vs 1 credit for a standard person search.** Budget accordingly when using role-based searches at scale. If you know the person's name, a standard person search at 1 credit is more cost-effective than a decision maker search at 2 credits.

2. **You are only billed for valid results — risky results are returned free but are less reliable.** A `risky` status means the email was found but could not be fully verified. These emails may still work, but they carry higher bounce risk. Do not treat risky results as equivalent to valid ones — consider additional verification or a more cautious sending approach for risky addresses.

3. **Real-time person searches can take up to 180 seconds — set your HTTP timeout accordingly.** The default timeout in many HTTP clients is 30 seconds, which will cause requests to fail prematurely. Set a minimum 180-second timeout for all search endpoints. If you are building a user-facing integration, show a loading state and consider using webhooks for async notification instead of blocking the UI.

4. **Bulk search credits are charged on download, not on job creation.** This means you can submit a large job, review the results summary, and decide whether to download (and pay) or