Skip to main content
Huntr gives you an agent (/research) and deterministic endpoints (search, enrichment, pages). Both use the same API key and credit balance.

​
Research agent (POST /research)

Best for: open-ended questions where you want Huntr to decide which sources to check and how to combine them.
Strengths
  • One call for account briefs, buyer research, competitive questions
  • Optional schema for structured top-level fields
  • Tiers (lite, standard, deep) control capability depth
Limits
  • One primary target per request
  • Not for bulk list + per-row enrichment
  • Price is per completed research run (see /pricing for current tiers)

​
Research tiers

​
Direct endpoints

Best for: repeatable workflows where your code (or Clay column) already knows the operation. Strengths
  • Predictable inputs and outputs
  • Lower cost for single-purpose lookups
  • Easy to chain in automations (search → enrich → email)

​
Cost intuition

When in doubt: if you can name the endpoint, call it directly. If you need judgment and synthesis, use /research.

​
MCP exposes the full API

The Huntr MCP server mirrors every REST endpoint as a tool — not just research:
  • Research: research
  • Companies: company_search, company_search_count
  • People: person_search, person_search_count, person_email
  • LinkedIn / X / Web: person_linkedin, tech_stack, job_postings, company_contact, and more
  • Meta (free): get_pricing, get_balance, get_usage
Agents should call direct tools for known lookups and research for open-ended synthesis on one target. See the full tool list.

​
Next step