Skip to main content
Huntr is one API with multiple workflow shapes. Pick based on what you know and how many entities you are working with.

​
Decision table

Your goalUse thisWhy
Research one company, person, team, or business questionPOST /researchAgent selects sources, gathers context, synthesizes an answer
Build a list of companies matching ICP filtersPOST /company-searchStructured filters, pagination, per-result pricing
Find people across companies or at one employerPOST /person-searchTitle, employer, skills, location filters
Get one field you already know you need (email, tech stack, jobs)Direct enrichment endpointCheaper and faster than routing through /research
Scrape or analyze a specific public pagePOST /page-scrape or POST /page-analyzeDeterministic URL in, structured content out
Let an AI agent in your editor call HuntrHuntr MCPTools for research, search, and enrichment

​
The one-entity rule for /research

/research is optimized for one primary target and one decision:
  • Account brief before a meeting
  • Buyer research on a person or small team
  • Competitive or diligence question with a clear scope
  • Buying-signal investigation with a date range
It is not the right tool for:
  • “Find 200 CTOs and their emails”
  • “Enrich every row in this CSV”
  • Multi-company list building with per-row paid enrichment
Those workflows hit the research request budget and return: 
{
  "success": false,
  "code": "BULK_ENRICHMENT_REQUIRED",
  "price": 0,
  "recommended_workflow": [
    { "endpoint": "/company-search", "purpose": "Build a company list" },
    { "endpoint": "/person-search", "purpose": "Find relevant people" },
    { "endpoint": "/person-email", "purpose": "Find an email per person" }
  ]
}
Rejected requests are not charged.

​
Company-first vs person-first

Most outbound workflows are company-first:
  1. Find accounts that match your ICP (/company-search).
  2. Find people at those accounts (/person-search with currentCompanyWebsite).
  3. Enrich contacts (/person-email, /person-linkedin).
Use /research when you need synthesis across sources — not just raw fields — for a single account or buyer.

​
Sync vs async research

ModeHowWhen
Sync (default)POST /research returns 200 with the resultMost requests complete in seconds
AsyncAdd callback_url; API returns 202 immediatelyLong-running deep research, webhook-driven pipelines
Poll async status at GET /research/{request_id}/status or wait for the callback POST.

​
Next step