> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/superagents/batches/map.md).

# Map

Run the same task over many inputs in parallel.

A **Map** batch runs the same task over many inputs, in parallel. Each input gets its own run, each run produces a score or result, and the results are combined when every run has finished.

## When it's used

Use Map when you have a list of things to process the same way, and each one is small enough for a single worker. For example:

* Scoring each of 500 stocks on a quality metric
* Checking every claim in a research note against its source
* Extracting the same fields from each filing in a set

## How it works

1. The superagent writes one brief that applies to every input, and supplies the list of inputs.
2. A small pool of workers works through the list in parallel, reusing workers as they finish, rather than creating one worker per input.
3. Each run produces a score.
4. When all the runs are done, the scores are combined and the superagent is notified once.

## What you see

On the Map, the batch shows as one tile with its progress. Its results view is a **score chart** of each run's score.

## Example request

> Score every stock in the S\&P 500 on our quality factor and give me the top and bottom 20.

For a deep analysis of each input that needs a whole team rather than one worker, such as a full review of each portfolio company, use a [Survey](/zerve-docs/superagents/batches/survey.md) instead.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/superagents/batches/map.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.