AI GTM research API

GTM research your system can call.

Huntr helps GTM teams stop stitching together research, enrichment, contacts, and signals across disconnected tools. Use it when a workflow needs sales-ready context, not another raw data feed.

Get API key View API reference

GTM inputs Accounts, leads, signals

Huntr API Research + exact data

Your workflow CRM, agents, outbound

Why GTM teams keep stitching tools together

Most GTM stacks already have databases, sequencers, CRMs, and automation tools. The painful gap is everything between raw data and a useful next action: what the account does, who matters, what changed, whether the signal is real, and what a rep or workflow should do next.

Layer	What it gives you	What is still missing
Data provider	Known fields and enrichment	Interpretation and sales relevance
CRM	Records, ownership, pipeline state	External account context
Sequencer	Campaign execution	Research before enrollment
Huntr	Account context, enrichment, contacts, and signals	Your workflow decides the next action

From account question to GTM context

POST /researchGTM research prompt

curl https://api.tryhuntr.com/research \
  -H "x-api-key: hntr_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tier": "standard",
    "prompt": "Research Figma for GTM planning. Return company context, recent signals, likely buyer priorities, and recommended outbound angles."
  }'

What your GTM workflow receives

Company context

What the company does, who it serves, how it positions itself, and what may matter to a seller, operator, or internal agent.

Lead context

Role-level research that explains why a specific person may care about a workflow, problem, or buying motion.

Buying signals

Recent public context such as launches, hiring, expansion, funding, partnerships, or other signals worth reviewing.

Decision support

Concise notes, risk flags, fit evidence, outbound angles, and CRM-ready summaries for human or system review.

Representative output modes

GTM briefExample shape

{
  "account_context": "What the company does and why it may fit the workflow.",
  "lead_context": "Why this role may care and what responsibilities are likely relevant.",
  "signals": ["public signal with business relevance", "another signal worth human review"],
  "recommended_action": "Enroll, review manually, enrich further, or skip.",
  "message_angle": "A concise angle grounded in the research.",
  "risk_notes": "What should not be claimed without confirmation."
}

Where teams use it

Outbound systems

Run research before a lead enters Aimfox, Smartlead, Instantly, Apollo, or a custom sequence builder.

CRM and RevOps workflows

Write account notes, qualification context, and buyer signals into CRM fields, review queues, or routing logic.

Agency operations

Standardize research across clients so campaign teams do not rebuild the same manual process every launch.

Internal AI agents

Give assistants and automation tools a research endpoint they can call when they need external GTM context.

Prompt library

Account brief

Research this account for outbound. Return what they do, likely priorities, recent signals, objections, and relevant outreach angles.

Lead research

Research this person and company. Explain their role, likely responsibilities, and why our workflow may be relevant to them.

Buying signal review

Find recent public signals that suggest this account may be investing in sales, data, automation, hiring, or market expansion.

CRM note

Create a compact CRM research note with business summary, decision context, recent signals, recommended action, and risk notes.

Agent tool call

Given this account and workflow, return the external context an internal AI assistant needs before recommending the next action.

When not to use Huntr

Raw search results are enough

If the workflow only needs links or snippets, use a search API. Huntr is for teams that need research context their workflow can act on.

You need one fixed field only

If every output is a single known attribute, a narrow enrichment lookup may be enough. Huntr is stronger when research, enrichment, contacts, and signals need to work together.

No human or system review exists

Research can guide action, but high-stakes outbound claims, qualification decisions, and strategic conclusions should still be reviewable.

The workflow belongs in a spreadsheet

If the team wants the entire process in a table UI, use the tool that best owns that interface. Huntr is strongest when research must flow into an existing system.

FAQ

Is Huntr for enrichment or research?

Both can appear in the workflow, but the core value is research: interpreting company, lead, and signal context for a GTM decision.

Can this power internal GTM agents?

Yes. Use Huntr when an assistant needs external account context before recommending an action or producing a workflow note.

Can agencies use this across clients?

Yes. Agencies can standardize the research step while keeping campaign delivery in their existing tools and reporting systems.