timzinin-com Lead List Cleaner API
The Lead List Cleaner API from timzinin-com — 1 operation(s) for lead list cleaner.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-lead-list-cleaner-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Zinin M2M Hub Lead List Cleaner API
description: Pay-per-call data & tool APIs
version: 1.0.0
x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Lead List Cleaner
paths:
/api/lead-list-cleaner:
post:
summary: Lead List Cleaner - Dedupe, DNS & Email Hygiene
description: Normalize mixed lead rows, deduplicate domains and emails, check DNS/MX evidence, score retained leads, and return every rejection, confidence gap, safe action, and run summary for auditable CRM staging.
operationId: call_lead_list_cleaner
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.020000'
protocols:
- x402: {}
network: eip155:8453
payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
requestBody:
required: true
content:
application/json:
schema:
title: Lead List Cleaner input
description: Turn any scraper's raw dataset into a clean, scored lead list — dedupe rows, kill dead emails and dead domains, rank the rest by hotness. Runs standalone or as an Integration bolted onto Google Maps / lead scrapers.
type: object
schemaVersion: 1
properties:
datasetId:
sectionCaption: Choose one lead source
sectionDescription: Use direct Items, a Dataset selected with READ permission, or a public JSON URL. Direct Items take priority; leave unused source fields empty.
title: Dataset ID
type: string
description: Pick another Actor's dataset to clean (e.g. a Google Maps or lead-scraper run). Ignored when 'items' is set. Picking it here — not just pasting the ID — is what grants this run's token READ access to that dataset. When this Actor is added as an Integration on another Actor, this field is filled in automatically from the triggering run.
editor: resourcePicker
resourceType: dataset
resourcePermissions:
- READ
example: your_dataset_id
datasetUrl:
title: Dataset URL
type: string
description: Public URL returning a JSON array of lead rows. Used only when both 'items' and 'datasetId' are empty.
editor: textfield
example: https://api.apify.com/v2/datasets/YOUR_PUBLIC_DATASET_ID/items?clean=true
items:
title: Items
type: array
description: Raw lead rows to clean directly, one object per lead — any shape works (Google Maps scraper export, CSV turned into JSON, anything with an email/website/phone somewhere in it). Takes priority over 'datasetId' and 'datasetUrl'.
editor: json
items:
type: object
prefill:
- title: Shopify
categoryName: Software company
website: https://www.shopify.com
phone: +1 888-746-7439
url: https://www.google.com/maps/place/Shopify
- name: HubSpot
email: press@hubspot.com
phoneNumber: +1 888-482-7768
link: https://www.hubspot.com
- companyName: Zoom Video Communications
description: Video conferencing platform. Contact us at info@zoom.us for enterprise sales.
domain: zoom.us
- title: Shopify Inc
website: https://shopify.com
phone: +1 888-746-7439
- title: Stripe
categoryName: Payment processor
website: https://stripe.com
phone: +1 888-926-2289
emails:
- support@stripe.com
example:
- name: Example Co
email: sales@example.com
website: https://example.com
checks:
sectionCaption: Cleaning and scoring policy
sectionDescription: Choose deterministic pipeline stages, the buyer-owned score threshold, and a hard row cap. Disabled checks remain visible evidence gaps.
title: Checks to run
type: array
description: Pipeline stages to run, in order. 'dedupe' collapses rows sharing the same domain/email. 'email' verifies syntax + MX. 'domain' verifies the domain is alive. 'score' computes the hotness score used for the 'minScore' cutoff.
editor: select
items:
type: string
enum:
- dedupe
- email
- domain
- score
enumTitles:
- Dedupe
- Email verify (syntax + MX)
- Domain alive check
- Hotness score
default:
- dedupe
- email
- domain
- score
prefill:
- dedupe
- email
- domain
- score
example:
- dedupe
- email
- domain
- score
minScore:
title: Minimum score
type: integer
description: Drop leads scoring below this threshold (0-100) from the clean, billed output. They still show up as free rejected rows with a reason.
default: 0
example: 40
minimum: 0
maximum: 100
maxRows:
title: Max rows
type: integer
description: Safety cap on how many input rows this run will process, regardless of source.
default: 1000
example: 100
minimum: 1
maximum: 100000
responses:
'200':
description: Actor run succeeded and payment settled
content:
application/json:
schema:
type: object
properties:
results:
type: array
items:
type: object
description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
meta:
type: object
properties:
run_ms:
type: integer
description: Actor run duration in milliseconds
item_count:
type: integer
description: len(results)
settled:
type: boolean
description: Whether the x402 payment was confirmed settled by the facilitator
transaction:
type:
- string
- 'null'
description: On-chain settlement transaction hash, null if unsettled
required:
- run_ms
- item_count
- settled
- transaction
required:
- results
- meta
'400':
description: Malformed PAYMENT-SIGNATURE header or request body
'402':
description: Payment required or invalid — see PAYMENT-REQUIRED header
'409':
description: Payment payload already used
'502':
description: Actor run failed
'504':
description: Actor run timed out
tags:
- Lead List Cleaner