Clay

Huntr is API-native — use it as an HTTP enrichment source in Clay without moving your workflow into another platform.

When to use Huntr in Clay

Clay column goal	Huntr endpoint
Account research brief	`POST /research`
Company list from ICP filters	`POST /company-search`
Find people at a company	`POST /person-search`
Work email	`POST /person-email`
Tech stack	`POST /company-tech-stack`
Hiring signal	`POST /company-jobs`

HTTP API column setup

Add an HTTP API enrichment column in Clay
Set method to POST
URL: https://api.tryhuntr.com/{endpoint} (e.g. /person-email)
Headers: x-api-key: {{your_huntr_key}}
Body: JSON with Clay {{column}} references

Example body for email finding:

{
  "first_name": "{{first_name}}",
  "last_name": "{{last_name}}",
  "company_domain": "{{domain}}"
}

Research columns

For narrative account briefs, call /research with a prompt that includes Clay fields:

{
  "prompt": "We sell {{your_product}}. Research {{company_name}} ({{domain}}) for buying signals from the last 12 months and practical outreach angles.",
  "tier": "standard"
}

Map the result field into your table.

Do not run /research on every row for bulk email finding — use /person-email per row instead. /research is for one-off synthesis.

Compare to Claygent

Huntr is built as an intelligence API (REST + MCP), not a Clay-only agent. You get the same research capabilities in n8n, your product, or Cursor — with per-request pricing and no workspace lock-in.

Getting started

Concepts

Guides

Build with AI

Integrations

Reference

When to use Huntr in Clay

HTTP API column setup

Research columns

Compare to Claygent

Next step

​When to use Huntr in Clay

​HTTP API column setup

​Research columns

​Compare to Claygent

​Next step

When to use Huntr in Clay

HTTP API column setup

Research columns

Compare to Claygent

Next step