> 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_manage.md).

# Exa Search Monitors Manage

Blocks for getting, listing and deleting Exa Search Monitors.

## Exa Delete Search Monitor

### What it is

Permanently delete an Exa Search Monitor, stopping its runs

### How it works

This block sends `DELETE /monitors/{monitor_id}` to Exa, which permanently removes the monitor and stops its scheduled runs. It outputs the monitor as it was just before deletion; `monitor_id` falls back to the ID you passed if Exa returns none. The block does not charge for the call. The deletion cannot be undone, so the block is flagged as an irreversible action. 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 |
| ----------- | --------------------------------------------- | ---- | -------- |
| monitor\_id | The monitor to delete. This cannot be undone. | str  | Yes      |

### Outputs

| Output      | Description                           | Type    |
| ----------- | ------------------------------------- | ------- |
| error       | Error message if the operation failed | str     |
| monitor\_id | ID of the deleted monitor             | str     |
| monitor     | The monitor as it was when deleted    | Monitor |

### Possible use case

**Project Cleanup**: Delete a monitor once the topic it watched is no longer relevant.

**Workflow Teardown**: Remove the monitor a workflow created when that workflow is retired, so Exa stops posting to its webhook.

**Replacing a Monitor**: Delete an old monitor after creating a replacement with a better query.

***

## Exa Get Search Monitor

### What it is

Get an Exa Search Monitor's query, schedule, webhook and status

### How it works

This block sends `GET /monitors/{monitor_id}` to Exa and returns the monitor's ID, status, next scheduled run and the full monitor (query, result count, domains, content options, period, output schema, metadata and webhook). `status` is `active`, `paused` or `disabled`; Exa sets `disabled` itself after repeated authentication failures. `next_run_at` is empty for a manual-only monitor. If Exa's response reports a `costDollars` total, the block bills it at 150 credits per USD; otherwise the call is free. 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 |
| ----------- | -------------------- | ---- | -------- |
| monitor\_id | The monitor to fetch | str  | Yes      |

### Outputs

| Output        | Description                                         | Type    |
| ------------- | --------------------------------------------------- | ------- |
| error         | Error message if the operation failed               | str     |
| monitor\_id   | The monitor's ID                                    | str     |
| status        | active, paused or disabled                          | str     |
| next\_run\_at | Next scheduled run (ISO 8601); empty if manual-only | str     |
| monitor       | The full monitor                                    | Monitor |

### Possible use case

**Health Check**: Check whether a monitor is still active or has been disabled by Exa before relying on its deliveries.

**Schedule Lookup**: Read `next_run_at` to tell users when the next batch of results will arrive.

**Config Audit**: Fetch a monitor's query, domains and webhook to confirm they match what a workflow expects.

***

## Exa List Search Monitors

### What it is

List Exa Search Monitors, filtered by status, name or metadata

### How it works

This block sends `GET /monitors` to Exa with the status, name, limit and cursor filters you set; each metadata pair becomes a `metadata[key]=value` query parameter, and a monitor must match all of them. It returns the page as a list and also outputs each monitor one at a time. When `has_more` is true, pass `next_cursor` back as `cursor` to fetch the next page. The block does not charge for the call. 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 |
| -------- | -------------------------------------------------------------------------------- | ---------------------------------- | -------- |
| status   | Only list monitors in this status                                                | "active" \| "paused" \| "disabled" | No       |
| name     | Only list monitors whose name contains this text (case-insensitive)              | str                                | No       |
| metadata | Only list monitors whose metadata has all of these key-value pairs (exact match) | Dict\[str, str]                    | No       |
| limit    | Monitors per page (1-100)                                                        | int                                | No       |
| cursor   | Cursor from a previous page's next\_cursor                                       | str                                | No       |

### Outputs

| Output       | Description                           | Type                      |
| ------------ | ------------------------------------- | ------------------------- |
| error        | Error message if the operation failed | str                       |
| monitors     | Monitors on this page                 | List\[SearchMonitorModel] |
| monitor      | Each monitor, one at a time           | Monitor                   |
| has\_more    | Whether another page exists           | bool                      |
| next\_cursor | Pass as cursor to fetch the next page | str                       |

### Possible use case

**Inventory**: List every monitor tagged with a given metadata value, such as a team or client ID.

**Status Review**: List disabled monitors to find ones that need their webhook or settings fixed.

**Bulk Processing**: Page through all monitors and run a follow-up block, such as Get Search Monitor Run, for each one.

***


---

# 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_manage.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.
