> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhuntr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose your workflow

> Pick the right Huntr endpoint family for your GTM goal.

Huntr is one API with multiple workflow shapes. Pick based on **what you know** and **how many entities** you are working with.

## Decision table

| Your goal                                                             | Use this                                    | Why                                                           |
| --------------------------------------------------------------------- | ------------------------------------------- | ------------------------------------------------------------- |
| Research **one** company, person, team, or business question          | `POST /research`                            | Agent selects sources, gathers context, synthesizes an answer |
| Build a **list** of companies matching ICP filters                    | `POST /company-search`                      | Structured filters, pagination, per-result pricing            |
| Find **people** across companies or at one employer                   | `POST /person-search`                       | Title, employer, skills, location filters                     |
| Get **one field** you already know you need (email, tech stack, jobs) | Direct enrichment endpoint                  | Cheaper and faster than routing through `/research`           |
| Scrape or analyze a **specific public page**                          | `POST /page-scrape` or `POST /page-analyze` | Deterministic URL in, structured content out                  |
| Let an **AI agent** in your editor call Huntr                         | [Huntr MCP](/build-with-ai/huntr-mcp)       | Tools for research, search, and enrichment                    |

## The one-entity rule for `/research`

`/research` is optimized for **one primary target** and **one decision**:

* Account brief before a meeting
* Buyer research on a person or small team
* Competitive or diligence question with a clear scope
* Buying-signal investigation with a date range

It is **not** the right tool for:

* "Find 200 CTOs and their emails"
* "Enrich every row in this CSV"
* Multi-company list building with per-row paid enrichment

Those workflows hit the research request budget and return:

```json theme={null}
{
  "success": false,
  "code": "BULK_ENRICHMENT_REQUIRED",
  "price": 0,
  "recommended_workflow": [
    { "endpoint": "/company-search", "purpose": "Build a company list" },
    { "endpoint": "/person-search", "purpose": "Find relevant people" },
    { "endpoint": "/person-email", "purpose": "Find an email per person" }
  ]
}
```

**Rejected requests are not charged.**

## Company-first vs person-first

Most outbound workflows are **company-first**:

1. Find accounts that match your ICP (`/company-search`).
2. Find people at those accounts (`/person-search` with `currentCompanyWebsite`).
3. Enrich contacts (`/person-email`, `/person-linkedin`).

Use `/research` when you need **synthesis** across sources — not just raw fields — for a single account or buyer.

## Sync vs async research

| Mode               | How                                               | When                                                 |
| ------------------ | ------------------------------------------------- | ---------------------------------------------------- |
| **Sync** (default) | `POST /research` returns `200` with the result    | Most requests complete in seconds                    |
| **Async**          | Add `callback_url`; API returns `202` immediately | Long-running deep research, webhook-driven pipelines |

Poll async status at `GET /research/{request_id}/status` or wait for the callback POST.

## Next step

* [Research vs direct endpoints](/concepts/research-vs-direct-endpoints) — deeper comparison
* [Research Agent guide](/guides/research-agent) — write better prompts
* [Company search guide](/guides/company-search) — list-building patterns