Lead search filters
Availability:
leads/searchis a catalog-tier route and returns503by default (CATALOG_ROUTES_ENABLED=0). This recipe is kept for when the route is re-enabled.
Question: "Find CTOs at software companies in Florida."
Tool
POST /api/v1/leads/search or MCP leads_search
{
"industry": "software",
"state": "FL",
"title": "CTO",
"limit": 25
}
Default price: $0.100 per call. Bill-on-match on zero rows — empty
result sets are refunded. Identical filter payloads may return cache_hit: true
within the request store TTL (24h default).
Filter composition
| Filter | Use when |
|---|---|
industry |
Vertical scoping (software, healthcare, …) |
state / city |
Geo narrowing |
title |
Role targeting (CTO, VP Sales, …) |
company_size |
Employee band when supported |
limit |
Page size (1–100; start with 25) |
cursor |
Next page from prior response |
Always send at least one of industry, geo, or title — avoid empty-body searches.
Pagination
- First call with
limit: 25, no cursor. - If response includes a cursor, pass it on the next call unchanged.
- Stop when the user has enough rows or cursor is absent.