> For the complete documentation index, see [llms.txt](https://visi-digital-internasional.gitbook.io/geo-prospector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visi-digital-internasional.gitbook.io/geo-prospector/geo-prospector-nl/prospectiewerkstromen/single-category.md).

# Zoeken in één categorie

Gebruik deze workflow voor één bedrijfscategorie in één geografisch doelgebied.

## Procedure

1. Selecteer één doelcategorie.
2. Kies land, regio en stad.
3. Stel het aantal records in.
4. Schakel het duplicatenfilter in.
5. Schakel Email Finder in wanneer e-mailverrijking vereist is.
6. Selecteer de gegevensvertraging.
7. Start de zoekopdracht.

## Verwerkingsfasen

Geo Prospector kan:

1. Potentiële bedrijven ontdekken.
2. Kandidaten vooraf filteren.
3. Duplicaten verwijderen.
4. Records selecteren voor verrijking.
5. Voer Email Finder uit.
6. Sla de uiteindelijke resultaten op.
7. Leg het uiteindelijke kredietverbruik vast.

De voortgang kan tijdelijk worden gepauzeerd tijdens verrijking of afronding. Wacht op de eindstatus voordat u de resultaten bekijkt.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://visi-digital-internasional.gitbook.io/geo-prospector/geo-prospector-nl/prospectiewerkstromen/single-category.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.