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)

• 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

• What it does: Takes a person's name and company or domain, returns a verified email address with status (valid, risky, not_found, or blacklisted)
• Endpoint:

  POST /v5.1/search/person.json

  with

  full_name

  (or

  first_name

  +

  last_name

  ) and

  company_name

  or

  domain

  in the request body
• Credit cost: 1 credit per valid result — risky and not-found results are free
• Key behavior: Real-time searches can take up to 180 seconds — set your HTTP timeout accordingly. Duplicate searches within 30 days are free (not re-charged)
• Use cases: Finding a specific decision-maker's email when you know their name and company, building targeted outbound lists for account-based outreach

• What it does: Finds up to 20 email addresses at a given company or domain
• Endpoint:

  POST /v5.1/search/company.json

  with

  company_name

  or

  domain

• Credit cost: 1 credit per search (returns up to 20 emails)
• Use cases: Building prospect lists from target company domains, finding all reachable contacts at an account, enriching account records with contact emails

• What it does: Role-based email search — finds contacts by job function category at a company. Returns person name, title, LinkedIn URL, and email
• Categories: ceo, engineering, finance, hr, it, logistics, marketing, operations, buyer, sales
• Endpoint:

  POST /v5.1/search/decision_maker.json

  with

  domain

  and

  category

• Credit cost: 2 credits per valid result (double the standard person search)
• Use cases: Finding the right department contact without knowing a name, account-based selling where you need to reach a specific function (e.g., "find me the head of engineering at acme.com")

• What it does: Extracts a verified email address from a LinkedIn profile URL
• Endpoint:

  POST /v5.1/search/linkedin.json

  with

  linkedin_url

• Credit cost: 1 credit per valid result
• Use cases: Converting LinkedIn prospects into contactable leads, enriching LinkedIn Sales Navigator exports with verified emails

• What it does: Validates an email address and returns a status of valid, risky, or invalid
• Endpoint:

  POST /v5.1/verify.json

  with

  email_address

• Credit cost: 0.2 credits per verification — repeated checks on the same email within 30 days are free
• Use cases: Cleaning email lists before outreach, reducing bounce rates, protecting sender reputation, validating leads before adding to CRM

• What it does: Process up to 100,000 rows per request asynchronously — supports JSON body or CSV/Excel file upload
• Endpoint:

  POST /v5.1/bulk/search.json

  (JSON) or

  POST /v5.1/bulk/upload.json

  (file upload)
• Key behavior: Async processing — approximately 1,000 rows in 5 minutes. Credits are charged only when you download results, not when you create the job. Webhook notifications via

  x-webhook-url

  header for completion alerts
• Use cases: Processing large prospect lists, batch-enriching CRM exports, high-volume email discovery campaigns

• What it does: Location-based lead discovery — find leads by geographic area
• Endpoints: Create a GeoLead search, Get Info on a search, Download Results
• Note: GeoLead Finder documentation is limited — expect some experimentation to understand the full feature set
• Use cases: Territory-based prospecting, finding local businesses in a geographic area, location-targeted lead generation

• What it does: Browser-based email finding from any website — find emails while browsing company websites or LinkedIn profiles
• Requirement: Requires login to anymailfinder.com in the same browser session
• Use cases: Prospecting while browsing target company websites, quick email lookup during research sessions, finding contact info without leaving the browser

• What it does: Count the number of known emails at a domain, place an order for the full list, and download the results
• Endpoints: Count (

  POST /v5.1/domain/count.json

  ), Order (

  POST /v5.1/domain/order.json

  ), Download (

  GET /v5.1/domain/download.json

  )
• Use cases: Assessing coverage at a target domain before committing credits, bulk domain email retrieval

• What it does: Report an incorrect email result back to Anymail Finder for correction
• Endpoint:

  POST /v5.1/report.json

• Use cases: Improving data quality by flagging bounced or incorrect emails, contributing to the platform's accuracy

• Base URL:

  https://api.anymailfinder.com/v5.1

• Authentication:

  Authorization: <your-api-key>

  header on all requests
• Format: JSON responses; all search endpoints use POST
• Rate limits: None — requests are queued and the system auto-scales. At high volume, requests are queued rather than rejected, so response times may increase
• Webhook support: Pass

  x-webhook-url

  header to receive async completion notifications (especially useful for bulk operations)
• Key endpoints:

  • POST /v5.1/search/person.json

    — find email by person name + company/domain (1 credit)

  • POST /v5.1/search/company.json

    — find up to 20 emails at a company/domain (1 credit)

  • POST /v5.1/search/decision_maker.json

    — find email by role category at a domain (2 credits)

  • POST /v5.1/search/linkedin.json

    — find email from LinkedIn URL (1 credit)

  • POST /v5.1/verify.json

    — verify an email address (0.2 credits)

  • POST /v5.1/bulk/search.json

    — bulk email search via JSON body (up to 100K rows)

  • POST /v5.1/bulk/upload.json

    — bulk email search via CSV/Excel file upload

  • POST /v5.1/domain/count.json

    — count known emails at a domain

  • POST /v5.1/domain/order.json

    — order full email list for a domain

  • GET /v5.1/domain/download.json

    — download ordered domain email list

  • POST /v5.1/report.json

    — report a bad email result
• Docs: API documentation available at anymailfinder.com

• Yearly billing saves 33% on all plans.
• Credit costs by operation: Person search = 1 credit, Decision Maker search = 2 credits, Email Verifier = 0.2 credits, Company/Domain search = 1 credit (up to 20 emails).
• Free for risky/not-found results — you only pay for valid emails. Risky results are returned but not charged.
• Duplicate searches within 30 days are free — re-searching the same person or email does not consume additional credits.
• Unused credits accumulate up to 2x your plan size — e.g., a Standard plan (1,000 credits/mo) can accumulate up to 2,000 credits maximum. Credits beyond that cap are forfeited.

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

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 discard. However, do not assume the job is "free" until download — plan for the credit cost when you submit, or you may be surprised when you try to download and lack sufficient credits.
5. GeoLead Finder documentation is incomplete — expect experimentation. The GeoLead Finder endpoints (Create, Get Info, Download Results) exist but have limited public documentation. Test with small requests first to understand input parameters, response formats, and credit costs before committing to large-scale geographic lead searches.
6. Catch-all domains may return a risky status even for valid mailboxes. Catch-all (or accept-all) domains are configured to accept email for any address at the domain, making it impossible to verify whether a specific mailbox exists. Anymail Finder returns

   risky

   for these because it cannot confirm deliverability to the specific address. If your target company uses a catch-all domain, you will consistently get risky results — this is expected behavior, not a data quality issue.
7. No rate limits does not mean instant responses at high volume — requests are queued. Anymail Finder has no explicit rate limits and the system auto-scales, but at high request volumes, requests enter a queue rather than being processed simultaneously. Response times will increase proportionally with volume. For large-scale operations, use the bulk endpoints rather than making thousands of individual API calls.
8. Chrome Extension requires an active login to anymailfinder.com in the same browser. The extension will not work if you are logged out of the Anymail Finder website. If the extension stops finding emails, check that your session has not expired. Credits are deducted from your account the same as API usage.
9. Credit accumulation is capped at 2x your plan size. Unused credits roll over month to month, but only up to twice your monthly allocation. For example, the Standard plan (1,000 credits/mo) can accumulate a maximum of 2,000 credits. Any credits beyond the cap are forfeited. If you consistently under-use your plan, consider downgrading rather than assuming credits will bank indefinitely.

• /sales-enrich

  — Cross-platform data enrichment strategy (multi-tool enrichment workflows, waterfall enrichment)

• /sales-deliverability

  — Email deliverability and verification strategy (SPF/DKIM/DMARC, warmup, inbox placement)

• /sales-prospect-list

  — Prospect list building strategy and best practices

• /sales-integration

  — Connect Anymail Finder to CRM, automation tools, or other platforms

• /sales-hunter

  — Hunter.io platform help (similar domain email search and verification)

• /sales-apollo

  — Apollo platform help (similar email finder with sales engagement)

• /sales-prospeo

  — Prospeo platform help (similar email finder with LinkedIn focus)

• /sales-tomba

  — Tomba platform help (similar email finder and verifier)

• /sales-enrichso

  — Enrich.so platform help (B2B data enrichment API with LinkedIn and company data)

• /sales-getprospect

  — GetProspect platform help (similar email finder and lead generation)

• /sales-minelead

  — Minelead platform help (similar email finder, verifier, and lead generation)

• /sales-skrapp

  — Skrapp platform help (similar email finder with LinkedIn integration)

• /sales-do

  — Not sure which skill to use? The router matches any sales objective to the right skill. Install:

  npx skills add sales-skills/sales --skills sales-do

1. Uses Decision Maker search:

   POST /v5.1/search/decision_maker.json

   with

   domain: "acme.com"

   and

   category: "marketing"

   — returns name, title, LinkedIn URL, and email
2. Checks the response status:

   valid

   means the email is verified with 97%+ delivery guarantee
3. Notes the cost: 2 credits for a valid decision maker result (vs 1 credit for a standard person search)
4. If the result is

   risky

   , recommends verifying separately with

   POST /v5.1/verify.json

   (0.2 credits) or cross-referencing the LinkedIn URL to confirm the person is still in-role
5. Provides the user with the contact's name, title, LinkedIn profile, and verified email for outreach Result: User has a verified marketing decision-maker contact at acme.com with LinkedIn profile for context, ready for personalized outreach

1. Uploads the CSV via

   POST /v5.1/bulk/upload.json

   with

   Authorization: <api-key>

   and

   x-webhook-url: https://myapp.com/webhook

   headers
2. Explains async processing: ~1,000 rows every 5 minutes, so 5,000 rows will take approximately 25 minutes
3. Notes that credits are not charged until the user downloads results — the user can review the job summary first
4. When the webhook fires (or the user polls for status), the results are ready for download
5. Advises filtering downloaded results: prioritize

   valid

   emails for outreach, handle

   risky

   with caution, discard

   not_found

6. Estimates credit cost: up to 5,000 credits if all results are valid (1 credit per person search), but risky/not-found results are free — actual cost depends on hit rate Result: User has a bulk-processed list of verified emails for 5,000 prospects, with clear status indicators and credits charged only for valid results

1. For individual verification:

   POST /v5.1/verify.json

   with

   email_address

   — returns valid, risky, or invalid (0.2 credits each)
2. For 200 emails, recommends bulk approach for efficiency — submit as JSON via

   POST /v5.1/bulk/search.json

   or upload as CSV
3. Estimates credit cost: 200 x 0.2 = 40 credits for verification — fits within even the Starter plan (50 credits/mo)
4. Explains status meanings:

   valid

   = safe to add to CRM and email (97%+ delivery guarantee),

   risky

   = may work but unverified (common for catch-all domains),

   invalid

   = do not email
5. Recommends segmenting: add

   valid

   to CRM immediately, hold

   risky

   for manual review or secondary verification, discard

   invalid

6. Notes that re-verifying any of these emails within 30 days is free — safe to re-check before a campaign launch Result: User has a cleaned, segmented email list with 200 addresses verified at a cost of 40 credits, ready for CRM import with bounce risks removed