> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/promote/prospector-guide.md).

# Using Prospector

Discover and enrich Dream 100 targets for outreach, partnerships, podcasts, blogs, and influence.

## Start discovery

Select a client, open **Promote → Prospector**, and enter the market context requested by the workflow.

## Costs

A discovery run costs 2,000 credits. Enrichment costs 100 credits per target. Review the target count before enriching a large list.

## Evaluate targets

Review relevance and the evidence returned for each target. Treat AI scoring as prioritization support, then verify the organization, audience, contact path, and fit before outreach.

## Use responsibly

Personalize outreach, respect the recipient’s policies, and do not represent unverified contact or audience data as fact.


---

# 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://help.rankability.com/promote/prospector-guide.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.