> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/search_monitors_batch.md).

# Exa Search Monitors Batch

Blocks for deleting, pausing or unpausing many Exa Search Monitors at once by filter.

## Exa Batch Search Monitors

### What it is

Delete, pause or unpause every Exa Search Monitor matching a name, status or metadata filter (previews by default)

### How it works

This block sends `POST /monitors/batch` to Exa with the action, a filter built from name, status and metadata, `dry_run` and `limit`. At least one filter must be set; the block refuses to act on every monitor at once. `dry_run` is on by default, so the first run only reports which monitors would be affected; turn it off to apply the action. Each call handles up to `limit` monitors (1-500); run it again while `has_more` is true. The block does not charge for the call. The block is flagged as an irreversible action because `delete` cannot be undone. It needs your own Exa API key and fails with a clear message on the platform's shared Exa key, since every user of that key shares one Exa account.

### Inputs

| Input    | Description                                                                                                     | Type                               | Required |
| -------- | --------------------------------------------------------------------------------------------------------------- | ---------------------------------- | -------- |
| action   | delete removes matching monitors permanently; pause stops their scheduled runs; unpause makes them active again | "delete" \| "pause" \| "unpause"   | Yes      |
| name     | Match monitors whose name contains this text (case-insensitive)                                                 | str                                | No       |
| status   | Match monitors in this status                                                                                   | "active" \| "paused" \| "disabled" | No       |
| metadata | Match monitors whose metadata has all of these pairs                                                            | Dict\[str, str]                    | No       |
| dry\_run | Only preview which monitors would be affected. Turn off to actually apply the action.                           | bool                               | No       |
| limit    | Most monitors to process in one call (1-500). Run again while has\_more is true to process the rest.            | int                                | No       |

### Outputs

| Output       | Description                                                  | Type       |
| ------------ | ------------------------------------------------------------ | ---------- |
| error        | Error message if the operation failed                        | str        |
| action       | The action requested                                         | str        |
| affected     | How many monitors were (or, in a dry run, would be) affected | int        |
| monitor\_ids | IDs of those monitors                                        | List\[str] |
| dry\_run     | Whether this was only a preview                              | bool       |
| has\_more    | More monitors match; run again to process them               | bool       |

### Possible use case

**Client Offboarding**: Delete every monitor whose metadata carries a departing client's ID, after checking the dry-run list.

**Pausing a Project**: Pause all monitors whose name contains a project name while that project is on hold.

**Resuming Work**: Unpause every paused monitor with a given metadata tag when the work starts again.

***


---

# 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://agpt.co/docs/integrations/block-integrations/search_monitors_batch.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.
