timzinin-com Lead List Qualifier API
The Lead List Qualifier API from timzinin-com — 1 operation(s) for lead list qualifier.
The Lead List Qualifier API from timzinin-com — 1 operation(s) for lead list qualifier.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-lead-list-qualifier-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Zinin M2M Hub Lead List Qualifier 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 Qualifier
paths:
/api/lead-list-qualifier:
post:
summary: Lead List Qualifier
description: Scores domains for buying readiness from several of our own signal sources in one call. Identity confidence is reported honestly as guessed when no override is supplied.
operationId: call_lead_list_qualifier
x-payment-info:
price:
mode: fixed
currency: USD
amount: '0.050000'
protocols:
- x402: {}
network: eip155:8453
payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
requestBody:
required: true
content:
application/json:
schema:
title: Lead List Qualifier input
type: object
schemaVersion: 1
properties:
domains:
title: Domains to qualify
type: array
description: Company domains to score (e.g. "stripe.com"). Each domain fires 4 parallel checks (tech stack, hiring, funding mentions, contact info), so this is capped at 25 per run.
editor: stringList
prefill:
- stripe.com
- shopify.com
maxItems: 10
role_keywords:
title: Role keywords (optional)
type: array
description: Highlight domains currently hiring for roles matching these words (passed to our company-hiring-radar Actor, e.g. "sales", "marketing"). Leave empty to skip role matching.
editor: stringList
prefill:
- sales
- marketing
maxItems: 10
company_name_overrides:
title: Company name overrides (optional, JSON)
type: object
description: 'By default this Actor guesses each domain''s ATS token / company name from the domain itself (e.g. "stripe.com" -> "stripe") for the hiring and funding checks — this is a best-effort heuristic, not a verified identity, and can be wrong. Use this field to override the guess for specific domains: {"my-startup.io": "mystartupinc"}.'
editor: json
prefill: {}
required:
- domains
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 Qualifier