Lyre Leads

Reviewed 58m ago.

tools

15 tools scanned

metadata

scanned

No findings.

• preview_search

  FREE, no account needed. Shows what ONE Google Maps search returns for a kind of business in a place: the first page, up to 20 real businesses with rating, review count, website and a partly hidden phone, plus what a full search adds and how the user can run it. Use it to show a user real results before they sign up, or to compare two wordings. Places look like "Houston, TX", "Copenhagen" or "Lyon, France"; a shared name picks the largest and lists the others. It is a sample from one point, not the market: for a whole city, the user connects their account and you use search_areas.

• find_areas

  FREE, no account needed. Look up the areas search_areas accepts in a country, most populous first, each with an id. Call without q to browse; call with no country to get the list of countries. When a place name is shared (the US list has four Houstons and thirteen Springfields), pass the id of the one the user means to search_areas.

• estimate_area_search

  FREE, no account needed. Size a search_areas run before starting it: how many grid points, and, when the user's account is connected, how many areas it already covers for the query (those are skipped). It cannot give an exact cost, because billing is 1 lead per NEW business found and nobody knows how many exist before looking.

• search_areas

  The search to use for coverage. Sweeps each area with a grid of map points live against Google Maps, as a background job, the same search the Lyre Leads Search page runs. In Houston this found 1,061 roofing contractors where paging from one centre found 255. Costs 1 lead per NEW business; listings the account already holds cost nothing (a small per-page minimum applies). Every new business is enriched, relevance-checked, its address verified, and enrolled in the monthly re-check automatically. Returns job_id: poll get_job_status with kind "search" until finished is true, then read the leads with get_search_results. If an area name fits more than one place, the call returns the candidates with ids and starts nothing: ask the user which one they mean and resend with that id. At most two searches run at once per account.

• get_search_results

  FREE. Read the leads a search_areas job found, with all enrichment fields, up to 500 per page. Accepts the same filters as the Lyre Leads database, passed as filters, e.g. {"relevanceYes": true, "hasVerifiedEmail": true, "noFBPixel": true}. Enrichment keeps landing for a while after the search finishes, so re-read if fields are still pending.

• search_leads

  Quick search of ONE city from its centre, answered in the same call: pulls 1-5 result pages (about 20 per page). Fine for a small town or a quick look; for real coverage of a city or several, use search_areas instead, which finds several times more. Saves results to the account database and starts background enrichment (50+ fields: emails, tech stack, analytics, ad pixels, contact channels). Costs 1 lead per NEW unique result; duplicates are free. Returns the raw results plus a search_id to poll for enriched data.

• list_results

  List saved lead results with their enrichment fields (email, verified status, tech stack, signals, AI score). Use search_id from search_leads to fetch one batch, and poll it while background enrichment fills in fields.

• get_balance

  Get the account lead balance and tier. The unit is a lead: 1 lead = 1 new business found by a search, with enrichment, relevance check, verified address and the monthly re-check included. Businesses you already hold: enrichment is five per lead, enrolling in the monthly re-check is two per lead. Named contacts found on the open web cost 2 leads each, charged only when a person is found. Email verification is included at no charge. Unused leads roll over, up to three months' allowance.

• estimate_list

  FREE, no account needed. Answers "what would it cost to find me N businesses, and what data comes with each one". Returns an exact cost in leads broken down by stage (search, enrichment, contact discovery), and when the user's account is connected its balance and the maximum businesses affordable right now, and the full list of data points each lead arrives with. THIS is the tool to use when a user asks what Lyre Leads can get them. Do NOT use count_saved_leads for that question: Lyre Leads generates leads on demand from a live Google Maps search and does not sell access to a stored pile of them, so a count of what an account already holds is not a measure of what is available.

• count_saved_leads

  FREE and exact. Counts leads THIS ACCOUNT has already searched and saved, matching any combination of filters, with a breakdown of how many are enriched, have an email, have a contact email, or have been relevance-checked. Use it to size a job over data the account already owns before spending: "how many of my saved roofers have no CRM and a verified email". CRITICAL: this is NOT an inventory of what Lyre Leads can find, and a small result here means the account has not searched much yet, nothing more. Never report this number to a user as the amount of data available, and never use it to answer "how many X do you have" — call estimate_list for that.

• enrich_leads

  Fetch each lead's website and extract 50+ fields: business email, social profiles, CMS, CRM, email-marketing platform, chat widget, booking system, ad pixels, analytics, schema, SSL, page load, domain age, mail host, and AI-crawler policy. Costs one lead per five businesses, on any business you hold, and does not enroll it. Every address it finds is verified at no extra charge. To keep businesses current, use enroll_leads instead. Runs in the background, returns a job id, poll it with get_job_status. Every field follows the three-state contract: a value, a confirmed absence, or unknown.

• enroll_leads

  Enroll leads in enrichment so they stay current: each lead is enriched now and re-checked about once a month for as long as the user keeps it, with change signals when something moves. Costs one lead per two businesses, paid once. Businesses a search found are already enrolled for free; already-enrolled leads and leads without a website are skipped at no cost. Use it for the imported or chosen leads the user cares about most. Runs in the background and returns a job id: poll get_job_status with kind "enrich".

• find_contacts

  For leads with a website but no named contact, search the open web for the people the business names (owner, founder, director), then resolve and verify their email. Costs 2 leads per named contact found, and nothing for a business where nobody is found; the run reserves 2 per business up front and settles on what it delivered. This is what reaches local business owners who are not in any LinkedIn-derived contact database. Returns a job id, poll with get_job_status. Outcomes per lead: verified (SMTP-confirmed), published (the address is printed on the company's own site but the domain is catch-all so SMTP cannot confirm it), catch_all (person named, no address obtainable), or searched (no name found).

• verify_emails

  SMTP-verify the business emails on saved leads through MillionVerifier. Included in every plan at no charge; a re-check within 90 days reuses the cached verdict. Runs in the background and returns a job id: poll get_job_status with kind "verify" until status is completed, then read the summary. Each address ends in one of four honest states: verified, catch_all (the domain accepts everything, so deliverability cannot be proven), unknown, or invalid. Never treat catch_all as verified.

• get_job_status

  Poll a background job started by search_areas, enrich_leads, enroll_leads (kind "enrich"), find_contacts or verify_emails. Pass the job id and its kind. Long jobs are normal: a grid search works through many map points, and enrichment fetches every website in the batch.