> ## Documentation Index > Fetch the complete documentation index at: https://exa.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The Exa API is served at https://api.exa.ai. Authenticate with `Authorization: Bearer $EXA_API_KEY` (or `x-api-key: $EXA_API_KEY`); create keys at https://dashboard.exa.ai/api-keys?utm_source=docs&utm_medium=docs&utm_campaign=markdown_instructions. Every way an agent can get access to Exa is described at https://exa.ai/auth.md. > Prefer the official SDKs, `exa-py` (`pip install exa-py`) and `exa-js` (`npm install exa-js`); both read `EXA_API_KEY` from the environment. > Tool-using agents can call Exa without writing code through the hosted MCP server at https://mcp.exa.ai/mcp, or install the Exa agent skill with `npx skills add exa-labs/agent-skills` (skill file: https://exa.ai/docs/skill.md). > The OpenAPI specs at https://exa.ai/docs/exa-spec.yaml and https://exa.ai/docs/team-management-spec.yaml are the source of truth for request and response schemas. # Batch action on monitors > Deletes, pauses, or unpauses the monitors that match the filter. Deletion is permanent. `dry_run` defaults to `true`, so a request only previews the affected monitors unless you set it to `false`. Repeat the request until `has_more` is `false` to process all matches. ## OpenAPI ````yaml exa-spec.yaml POST /monitors/batch openapi: 3.1.0 info: title: Exa Public API version: 2.0.0 servers: - url: https://api.exa.ai security: - apiKey: [] - bearer: [] paths: /monitors/batch: post: tags: - Monitors summary: Batch action on monitors description: >- Deletes, pauses, or unpauses the monitors that match the filter. Deletion is permanent. `dry_run` defaults to `true`, so a request only previews the affected monitors unless you set it to `false`. Repeat the request until `has_more` is `false` to process all matches. operationId: batchMonitors requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/BatchMonitorsRequest' responses: '200': description: Batch action result headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/BatchMonitorsResponse' '400': $ref: '#/components/responses/BadRequestResponse' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/ForbiddenResponse' '500': $ref: '#/components/responses/InternalServerErrorResponse' components: schemas: BatchMonitorsRequest: type: object properties: action: type: string enum: - delete - pause - unpause description: >- The action to perform on matching monitors. `delete` permanently removes them, `pause` sets their status to paused, and `unpause` sets their status to active. filter: type: object properties: name: type: string maxLength: 250 description: Filter by name (case-insensitive substring match) status: type: string enum: - active - paused - disabled description: Filter by monitor status metadata: type: object propertyNames: type: string additionalProperties: type: string maxLength: 1000 description: Filter by metadata key-value pairs (exact match, AND semantics) description: >- At least one filter field must be provided to prevent accidental bulk operations. dry_run: type: boolean description: >- When `true`, returns the monitors that would be affected without performing the action. Defaults to `true`. default: true limit: type: integer minimum: 1 maximum: 500 description: >- Maximum number of monitors to process in a single request. Defaults to 50, maximum 500. default: 50 required: - action - filter BatchMonitorsResponse: type: object properties: action: type: string enum: - delete - pause - unpause description: The action that was performed affected: type: integer description: The number of monitors affected by the action ids: type: array items: type: string description: The IDs of the monitors that were affected dry_run: type: boolean description: Whether this was a dry run has_more: type: boolean description: >- Whether there are more monitors matching the filter. If `true`, repeat the request to process the next batch. required: - action - affected - ids - dry_run - has_more additionalProperties: false ErrorResponse: type: object properties: requestId: type: string description: Unique identifier for the request. error: type: string description: Human-readable message describing the error. tag: type: string description: >- Machine-readable error tag identifying the failure. The set of tags is open-ended: new tags may be added at any time, so treat unrecognized tags as a generic error of the response's HTTP status. Known tags are listed as examples. required: - requestId - error - tag additionalProperties: false description: Standard error envelope returned by the Exa API for failed requests. headers: XRequestId: description: >- Unique identifier for the request. Matches the `requestId` field returned in response bodies that carry one. schema: type: string responses: BadRequestResponse: description: The request body or query parameters failed validation. headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' UnauthorizedResponse: description: The API key is missing or invalid. headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' ForbiddenResponse: description: >- The team is not permitted to use this endpoint (`TEAM_BLOCKED`), or the feature is not enabled for it (`FEATURE_DISABLED`). headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' InternalServerErrorResponse: description: An unexpected error occurred while processing the request. headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' securitySchemes: apiKey: type: apiKey name: x-api-key in: header description: >- Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer . bearer: type: http scheme: bearer description: >- Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer . ````