Skip to main content
Get an API key, run a research request, and understand what comes back.

1. Get an API key

Fastest path: open the Huntr dashboard, sign up, and copy your API key. API signup (for programmatic onboarding):
Click the verification link in your email. Your key is returned once — store it securely.
Never put your API key in browser code, public repos, or client-side apps. Server-side and agent tooling only.

2. Check your balance

See Billing and pricing for plan-aware pricing and usage guidance.

3. Run your first research request

POST /research takes one focused objective and returns a synthesized answer. Start with tier: "standard" for company-level research.
Example response:

4. Request structured output

When your workflow needs predictable top-level fields, pass a flat schema map. Keys become result fields; values describe what each field should contain.
The schema value is a field map, not JSON Schema. Nested schema definitions are not supported. Structured responses include a confidence object per field (live, model, or not_found). Fields marked not_found are returned as null.

5. Try a direct endpoint

When you know exactly what you need, direct endpoints are faster and cheaper than /research. Search companies and read total from the response:
Find a work email for one person:

Choose your workflow

Decide between /research and direct endpoints before you build.

Company search

Build ICP lists with structured filters and pagination.

Research agent

Write prompts that produce account-ready briefs.

Huntr MCP

Connect Huntr to Cursor, Claude, or Codex.