> ## Documentation Index > Fetch the complete documentation index at: https://developer.moltsets.com/llms.txt > Use this file to discover all available pages before exploring further. # Search for People > Search MoltSets's contact database to find people by name, role, company, industry, country, seniority, or department. Use `query` for free-text cross-field search across name, company, title, and headline (put names and role keywords here), and the categorical filters (`country`, `seniority`, `industry`, `department`/`functional_area`) to narrow results. Combine query with filters for best precision. Returns ranked contact records — higher `_score` means a stronger match. Use this to build lead lists, identify decision-makers at target accounts, or populate outbound sequences with verified contact data. ## OpenAPI ````yaml /openapi.json post /search_people openapi: 3.1.0 info: title: MoltSets API version: 1.0.0 description: >- Identity resolution API. Resolve emails, LinkedIn profiles, IP addresses, and emails into enriched contact and company data. servers: - url: https://api.moltsets.com/api/v1/tools description: Production security: - bearerAuth: [] tags: - name: Search description: >- Search and filter company and business profiles by name, domain, industry, size, or revenue. - name: Get Valid Emails description: Resolve and enrich valid business and personal email addresses. - name: Get Carrier-Verified Mobile Phones description: Enrich carrier-verified mobile phone numbers. - name: Get Full Business Profile description: Resolve identifiers to full business profiles and company firmographics. - name: Get Ad Audience description: >- Resolve identifiers to hashed email (HEM) and mobile advertising IDs (MAIDs) for audience matching. - name: Get Company description: Resolve IP addresses to company data. - name: Account description: Account management tools. Free — do not consume credits. paths: /search_people: post: tags: - Search summary: Search for People description: >- Search MoltSets's contact database to find people by name, role, company, industry, country, seniority, or department. Use `query` for free-text cross-field search across name, company, title, and headline (put names and role keywords here), and the categorical filters (`country`, `seniority`, `industry`, `department`/`functional_area`) to narrow results. Combine query with filters for best precision. Returns ranked contact records — higher `_score` means a stronger match. Use this to build lead lists, identify decision-makers at target accounts, or populate outbound sequences with verified contact data. operationId: searchBusinessProfiles requestBody: required: false content: application/json: schema: type: object properties: query: type: string description: >- Full-text search across full_name, first_name, last_name, company name, title (~85% filled), and headline (~65% filled) using cross-field matching. Multi-word queries distribute terms across fields — "John Smith" matches first_name: John AND last_name: Smith rather than either alone. Job title and role keywords belong here — both the title field (e.g. "Account Executive", "Head of Sales", "Data Scientist", "Software Engineer", "Marketing Lead") and the headline field (e.g. "Helping SaaS companies grow", "B2B sales leader") are searched. For seniority level (VP, Director, C-suite) use the seniority filter instead; use this field for specific role or function keywords. Combine with filters for precision — e.g. query: "Account Executive", country: "United States", seniority: "Senior". Extract names, company names, and role keywords from the human's request. Examples: "Jane Doe", "Account Executive Salesforce", "Head of Sales fintech", "Data Scientist", "software engineer Netflix", "recruiter London". Do NOT put categorical values like country or seniority here — use the dedicated filter params for those. company: type: string description: >- Full-text search across company name only. Do not put domain, industry, employee size, or revenue here — use the dedicated filter params for those. example: moltsets.com company_domain: type: string description: >- Exact domain filter. Omit the protocol (no https://). Prefer this over `query` when you have a known domain — it's a precise match. example: moltsets.com country: type: string description: >- Exact country name filter (~99% filled — most reliable filter). Must match the stored value exactly. Top values by volume: "United States", "India", "United Kingdom", "Brazil", "Canada", "France", "Mexico", "Australia", "China", "Spain", "Netherlands", "Italy", "Indonesia", "Germany", "Philippines", "Turkey", "South Africa", "Saudi Arabia", "Argentina", "Singapore", "United Arab Emirates", "Colombia", "South Korea", "Malaysia", "Poland", "Belgium", "Switzerland", "Ireland", "Sweden", "Denmark", "Norway", "Austria", "Portugal", "Israel", "New Zealand", "Finland", "Greece", "Hungary", "Romania", "Ukraine". Use the full English country name. example: United States seniority: type: string description: >- Exact seniority level filter (~60% filled). Map the human's language to one of these exact values: "Intern" (intern, trainee, student ambassador), "Entry" (entry-level, junior, associate, coordinator, analyst, assistant — most common), "Senior" (senior, experienced individual contributor), "Manager" (manager, supervisor, team lead, head of small team), "Director" (director, senior director), "VP" (vice president, VP, SVP, EVP), "Head" (head of department, chief of staff), "C Suite" (CEO, CTO, CFO, COO, CMO, CRO, president, chief), "Owner" (owner, founder, co-founder, principal), "Partner" (partner, managing partner). Use the exact string shown — note "C Suite" has a space, not a hyphen. enum: - Intern - Entry - Senior - Manager - Director - VP - Head - C Suite - Owner - Partner industry: type: string description: >- This field takes one exact value from the fixed list below, and it's currently about 60% filled in. When someone describes their industry in their own words, find the closest match from the list and type it in exactly as shown, including the capitalisation, spelling, and any punctuation (for example the ampersand in "Marketing & Advertising"). Use the cues in brackets to decide which value fits: Information Technology (tech, software, IT, SaaS, startup) Professional and Business Services (consulting, business services, staffing) Finance and Banking (finance, banking, fintech, investment, insurance) Education (school, university, edtech, e-learning) Health and Pharmaceuticals (healthcare, pharma, biotech, medical, hospital) Manufacturing (manufacturing, industrial, production) Government and Public Administration (government, public sector, military) Retail (retail, e-commerce, consumer goods) Food and Beverage (food, beverage, restaurant, CPG) Creative Arts and Entertainment (media, entertainment, arts, gaming) Non-Profit and Social Services (nonprofit, NGO, charity, social) Transportation and Logistics (logistics, supply chain, shipping, trucking) Construction (construction, real estate development, architecture) Tourism and Hospitality (travel, hotel, tourism, hospitality) Energy (energy, oil, gas, renewables, utilities) Marketing & Advertising (marketing, advertising, PR, digital marketing) Telecommunications (telecom, wireless, broadband) Real Estate (real estate, property) Automotive (automotive, car, vehicle) Media and Publishing (media, publishing, journalism, news) Agriculture (agriculture, farming, agtech) enum: - Information Technology - Professional and Business Services - Finance and Banking - Education - Health and Pharmaceuticals - Manufacturing - Government and Public Administration - Retail - Food and Beverage - Creative Arts and Entertainment - Non-Profit and Social Services - Transportation and Logistics - Construction - Tourism and Hospitality - Energy - Marketing & Advertising - Telecommunications - Real Estate - Automotive - Media and Publishing - Agriculture department: type: string description: >- This field takes one exact value from the fixed list below, and it's currently about 60% filled in. Note that it shares its data with the functional_area field, so populate one or the other, not both. When someone describes their department in their own words, find the closest match and type it in exactly as shown, including capitalisation and punctuation (for example the ampersand in "Medical & Health"). Use the cues in brackets to decide which value fits: Operations (ops, general, administration, management — this is the most common one) Sales (sales, business development, account management) Information Technology (IT, tech, software, engineering — use this for IT and tech roles) Education (teaching, academic, training) Engineering (engineering, R&D, product engineering) Finance (finance, accounting, treasury) Medical & Health (healthcare, medical, nursing, clinical) Marketing (marketing, growth, demand gen, content) Human Resources (HR, people, talent, recruiting) Design (design, UX, creative) Consulting (consulting, advisory, strategy) Legal (legal, compliance, counsel) enum: - Operations - Sales - Information Technology - Education - Engineering - Finance - Medical & Health - Marketing - Human Resources - Design - Consulting - Legal functional_area: type: string description: >- Exact functional area filter (~60% filled, co-populated with department — same doc counts, same enumerated values, sourced together). Use department or functional_area, not both. Use the exact string shown. enum: - Operations - Sales - Information Technology - Education - Engineering - Finance - Medical & Health - Marketing - Human Resources - Design - Consulting - Legal limit: type: integer description: >- Number of results to return (default: 10, max: 25). Increase when the human wants more options. default: 10 minimum: 1 maximum: 25 offset: type: integer description: >- Number of results to skip for pagination (default: 0). Use with limit to page through results — e.g. offset: 10 to get the second page of 10 results. default: 0 example: query: Account Executive country: United States seniority: Senior limit: 10 offset: 0 responses: '200': description: Success content: application/json: examples: found: summary: Data found value: results: results: - title: Senior Associate - Technical Director company: name: MoltSets size: '57' revenue: '1200000000' industry: Information Technology logo_url: >- https://cdn.mixrank.com/md5/0bb6181a215bac707d7af3276be5XXXXX website_url: https://moltsets.com linkedin_url: https://linkedin.com/company/moltsets country: United States headline: Senior Associate - Technical Director @ MoltSets full_name: John Smith last_name: Smith seniority: Senior first_name: John linkedin_url: https://linkedin.com/in/john-smith-123 business_email: john.smith@example.com current_industry: Information Technology linkedin_slug: john-smith-123 _id: john-smith-123 _score: 9.1714 total: 278 status: ok metadata: tokens_charged: 1 tokens_remaining: unlimited daily_results_remaining: 9876 '400': description: Bad Request content: application/json: schema: $ref: '#/components/schemas/ErrorBadRequest' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorUnauthorized' '404': description: Not Found content: application/json: schema: $ref: '#/components/schemas/ErrorNotFound' '422': description: Invalid Input content: application/json: schema: $ref: '#/components/schemas/ErrorInvalidInput' '429': description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorRateLimit' components: schemas: ErrorBadRequest: type: object properties: error: type: string example: Bad Request message: type: string example: >- The server cannot process the request due to a client error (400 Bad Request). ErrorUnauthorized: type: object properties: error: type: string example: Unauthorized message: type: string example: Invalid API key. ErrorNotFound: type: object properties: error: type: string example: Not Found message: type: string example: No match was found for the data provided. ErrorInvalidInput: type: object properties: error: type: string example: Invalid Input message: type: string example: Message describing the nature of the invalid input. ErrorRateLimit: type: object properties: error: type: string example: Too Many Requests message: type: string example: Rate limit exceeded. Maximum 100 requests per second. securitySchemes: bearerAuth: type: http scheme: bearer description: >- Pass your API key as a Bearer token. Keys follow the format `ms_XXXXXXXXXXX`. ````