Find companies and people
Use prospect filters and catalogue lookups, then add selected records to a Sheet.
Use the assistant or a connected AI client to describe companies or people you want to find. Specify the market, geography, company characteristics and relevant person roles. Leadbase's search operations use AI Ark for prospect data; provider credentials stay with Leadbase.
Choose and resolve filters
prospects.company_searchsearches companies.prospects.people_searchsearches public person profiles and employer data. Company-prefixed filters describe the employer.- Resolve industries, locations and technologies with
prospects.industry_lookup,prospects.location_lookupandprospects.technology_lookupbefore using those catalogue values. - Use the exact returned catalogue strings. Closed filters such as company type, department or seniority use the options in the current schema. Do not invent values.
Each search needs at least one meaningful filter. Read its current descriptor for the full input contract; unused nullable fields must be sent as null when required. Catalogue lookups do not consume credits.
Page and review the results
Search pages are zero-based. size is at most 100. Results include page, size, total, totalPages, returned, rejected, results and an optional-valued requestId. The request ID is for correlation, not candidate identity.
The total is the number of matches, not the number of records already saved in your Sheet. Check a sample against your criteria, deduplicate using stable company or person identity, and ask the assistant to insert the selected records into the intended Sheet. Searching does not itself create those rows.
Contact data is a separate action
Company and people search do not return work emails or phone numbers. Use an identified result with Contact discovery when those fields are needed.
Each normalized record returned by a search page consumes the configured prospect tariff; empty or failed requests consume none under that tariff. Other assistant usage is separate. Every new search page needs its own idempotency key. Recover an identical page with the same input and key after a lost response; do not silently duplicate a paid search with uncertain settlement.
See API and agents and Credits.