How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Exa

Exa Monitors API

The Monitors API from Exa — 6 operation(s) for monitors.

Documentation Provider Profile APIs.io OpenAPI GitHub

Exa Monitors API is one of 19 APIs that Exa publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Monitors. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 12 operations across 6 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.exa.ai.

12 operations 6 paths 32 schemas 2 DELETE4 GET2 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.exa.ai
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Exa Monitors API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (apiKey). It accepts HTTP bearer tokens (bearer). By default, every request must be authenticated.

  • apiKey — Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer .
  • bearer — Pass your Exa API key in the x-api-key header. You can also authenticate with Authorization: Bearer .

Paths & Operations 12

Across 6 paths, the API surfaces 12 operations — 2 DELETE, 4 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Monitors 12
POST
/monitors
Create a Monitor
createMonitor body → 201
GET
/monitors
List Monitors
listMonitors 5 params → 200
POST
/monitors/batch
Batch Action on Monitors
batchMonitors body → 200
GET
/monitors/{id}
Get a Monitor
getMonitor 1 param → 200
PATCH
/monitors/{id}
Update a Monitor
updateMonitor 1 param body → 200
DELETE
/monitors/{id}
Delete a Monitor
deleteMonitor 1 param → 200
POST
/monitors/{id}/trigger
Trigger a Monitor
triggerMonitor 1 param → 200
POST
/v0/monitors
Create a Monitor
monitors-create body → 201
GET
/v0/monitors
List Monitors
monitors-list 3 params → 200
GET
/v0/monitors/{id}
Get Monitor
monitors-get 1 param → 200
PATCH
/v0/monitors/{id}
Update Monitor
monitors-update 1 param body → 200
DELETE
/v0/monitors/{id}
Delete Monitor
monitors-delete 1 param → 200

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are CreateSearchMonitorResponse (12 properties), MonitorRun (11 properties), SearchMonitorContents (11 properties), SearchMonitor (11 properties). Each schema is shown below with its type and property counts.

MonitorRun
object
11 properties 11 required
SearchMonitorWebhookOutput
object
2 properties 1 required
JsonValue
Any JSON value.
ListSearchMonitorsResponse
object
3 properties 2 required
TriggerSearchMonitorResponse
object
1 property 1 required
CreateSearchMonitorResponse
object
12 properties 12 required
UpdateMonitor
object
4 properties
SearchMonitorTrigger
object
2 properties 2 required
CustomEntity
object
2 properties 2 required
UpdateSearchMonitorParameters
object
7 properties
CreateMonitorParameters
object
4 properties 3 required
Monitor
object
11 properties 11 required
SearchMonitorSearch
object
3 properties 1 required
SearchMonitorTriggerOutput
object
2 properties 2 required
SearchMonitor
object
11 properties 11 required
SearchMonitorWebhook
object
2 properties 1 required
MonitorBehavior
object
2 properties 2 required
CompanyEntity
object
1 property 1 required
ListMonitorsResponse
object
3 properties 3 required
ArticleEntity
object
1 property 1 required
BatchMonitorsResponse
object
5 properties 5 required
ResearchPaperEntity
object
1 property 1 required
SearchMonitorOutputSchemaOutput
Controls the format of the run output. Defaults to { "type": "text" } if not specified. When type is "text", the output is a plain text summary. When type is "…
PersonEntity
object
1 property 1 required
SearchMonitorOutputSchema
Controls the format of the run output. Defaults to { "type": "text" } if not specified. When type is "text", the output is a plain text summary. When type is "…
MonitorCadence
object
2 properties 1 required
SearchMonitorSearchOutput
object
3 properties 1 required
BatchMonitorsRequest
object
4 properties 2 required
Entity
SearchMonitorContents
object
Content extraction options applied to each search result. All fields are optional.
11 properties
CreateSearchMonitorParameters
object
6 properties 2 required
SearchMonitorContentsOutput
object
Content extraction options applied to each search result. All fields are optional.
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

exa-ai-monitors-api-openapi.yml Raw ↑

Other APIs Exa publishes across the network.

Exa Agent API
AE Profile APIs.io
Exa Answer API
AE Profile APIs.io
Exa Contents API
AE Profile APIs.io
Exa Enrichments API
AE Profile APIs.io
Exa Events API
AE Profile APIs.io
Exa Imports API
AE Profile APIs.io
Exa Items API
AE Profile APIs.io
Exa Monitors Runs API
AE Profile APIs.io
Exa Research API
AE Profile APIs.io
Exa Runs API
AE Profile APIs.io
Exa Search API
AE Profile APIs.io
Exa Searches API
AE Profile APIs.io
#Monitors
← Back to E APIs
API Details
ID
exa-ai:exa-ai-monitors-api
Base URL
https://api.exa.ai
Docs
https://exa.ai/docs/reference/search-api-guide
Provider
Exa
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=exa-ai-monitors-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/exa-ai-monitors-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Exa Monitors API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.