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
  • Billing is per completed research run; check /pricing for plan-aware tier and model prices

​
Research tiers

​
Direct endpoints

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

​
Contact APIs (direct)

​
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 live REST endpoints as tools:
  • Contact APIs: person_search, person_email, person_phone, reverse_email
  • Company APIs: company_search, tech_stack, job_postings
  • Research APIs: research
  • LinkedIn / X / Web APIs: person_linkedin_url, company_linkedin_url, person_linkedin, company_contact, and more
  • Meta: 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