Exa integration: operations for AI agents
Exa connects to Type.com as an integration. This page lists the 70 operations documented for Claude and Codex in Type.com: 34 read, 20 write, 16 destructive.
About Exa
Exa focuses on data extraction and search, helping teams gather, analyze, and visualize information from websites, APIs, or internal databases
Categories: Analytics & Data
How to connect Exa to Type.com
- Connect
- Access token
- Access
- Organization connection: one shared account for the workspace.
To add the connection, follow the steps in Space connections.
Documented operations
70 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.
70 operations listed.
Search
- Read
Search
Perform a search with an Exa prompt-engineered query and retrieve a list of relevant results. Optionally get contents.
POST /search
Contents
- Read
Retrieve web page contents
Fetch text and requested content fields for the supplied page URLs. This is a semantic read sent with POST and may consume vendor credits; it does not create a monitor, Webset or saved agent run.
POST /contents
Answer
- Write
Answer
Performs a search based on the query and generates either a direct answer or a detailed summary with citations, depending on the query type.
POST /answer
Public API
- Read
Find similar links (deprecated)
Find links similar to the provided URL and optionally retrieve their contents. Deprecated: prefer `/search` with a query describing the source.
POST /findSimilar
Monitors
- Read
List monitors
Lists all monitors for the authenticated team. Supports filtering by status and cursor-based pagination.
GET /monitors - Read
Get a monitor
Retrieves a single monitor by its ID.
GET /monitors/{id} - Read
Webset list Monitors
Lists all monitors for the Webset.
GET /v0/monitors - Read
Webset get Monitor
Gets a specific monitor.
GET /v0/monitors/{id} - Write
Create a monitor
Creates a Monitor that runs an Exa search on a schedule and sends new results to your webhook. Each run searches recent content and drops results that match what earlier runs already returned, so your webhook receives only new developments. The response includes a `webhookSecret` for verifying webhook signatures. It is returned only once, so store it securely.
POST /monitors - Write
Update a monitor
Updates an existing monitor. All fields are optional. For `search`, you can send a partial object containing only the fields you want to change. Set `trigger` to `null` to remove the schedule.
PATCH /monitors/{id} - Write
Trigger a monitor
Triggers a run immediately, regardless of the schedule. Works for monitors with status `active` or `paused`.
POST /monitors/{id}/trigger - Write
Webset create a Monitor
Creates a Monitor that searches for new Items for a Webset on a `cron` schedule in the given `timezone`.
POST /v0/monitors - Write
Webset update Monitor
Updates a monitor configuration.
PATCH /v0/monitors/{id} - Destructive
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.
POST /monitors/batch - Destructive
Delete a monitor
Deletes a monitor. This cannot be undone.
DELETE /monitors/{id} - Destructive
Webset delete Monitor
Deletes a monitor.
DELETE /v0/monitors/{id}
Runs
- Read
List monitor runs
Lists all runs for a monitor with cursor-based pagination. Runs are returned in reverse chronological order.
GET /monitors/{id}/runs - Read
Get monitor run
Retrieves a single run by its ID, including the full output if the run is completed.
GET /monitors/{id}/runs/{runId}
Agent
- Read
List agent runs
List Agent runs for your team, ordered from newest to oldest.
GET /agent/runs - Read
Get agent run
Retrieve a single Agent run by ID.
GET /agent/runs/{id} - Read
List run events
List stored events for an Agent run. Set `Accept: text/event-stream` to replay stored events as server-sent events. Use `cursor` for JSON pagination or `Last-Event-ID` for SSE replay.
GET /agent/runs/{id}/events - Write
Create agent run
Create an asynchronous Agent run. By default, the API returns the run object immediately. Set `Accept: text/event-stream` to stream run lifecycle events until the run reaches a terminal status.
POST /agent/runs - Write
Stop agent run and retain partial results
Complete a running Agent run early, returning the results gathered so far. You are billed for usage accrued before the stop. Currently supported only for `ultra` effort runs. If the run has already reached a terminal status, the API returns the existing run.
POST /agent/runs/{id}/stop - Destructive
Delete agent run
Delete a stored Agent run.
DELETE /agent/runs/{id} - Destructive
Cancel agent run without results
Cancel a queued or running Agent run immediately without returning any results. You are billed for usage accrued before cancellation. If the run has already reached a terminal status, the API returns the existing run.
POST /agent/runs/{id}/cancel
Batches
- Read
List batches
List batches for your team, ordered from newest to oldest.
GET /batches - Read
Get a batch
Retrieve a single batch by ID.
GET /batches/{id} - Write
Create a batch
Create a batch of requests to run asynchronously. Each request is dispatched to its target route and results are made available for download when the batch completes.
POST /batches - Destructive
Delete a batch
Soft-delete a batch in a terminal status.
DELETE /batches/{id} - Destructive
Cancel a batch
Request cancellation of a batch. The batch stops scheduling new requests and drains in-flight work before settling to `cancelled`. Cancelling a batch that is already `cancelling` or `cancelled` is idempotent and returns the batch unchanged. A batch that has already reached a terminal status (`completed` or `expired`) cannot be cancelled and the request fails with a 409.
POST /batches/{id}/cancel
Teams
- Read
Get team info
Returns information about the authenticated team, including current concurrency usage and limits.
GET /v0/teams/me
Websets
- Read
List all Websets
Returns a list of Websets. You can paginate through the results using the `cursor` parameter. You can filter results using the `search` parameter to find Websets by ID, external ID, or title.
GET /v0/websets - Read
Get a Webset
Returns a Webset by `id` or `externalId`, including its status, searches, imports, enrichments, and monitors. Pass `expand=items` to include up to the first 100 items in the response.
GET /v0/websets/{id} - Write
Create a Webset
Creates a new Webset with optional search, import, and enrichment configurations. The Webset will automatically begin processing once created. You can specify an `externalId` to reference the Webset with your own identifiers for easier integration.
POST /v0/websets - Write
Update a Webset
Updates the `title` or `metadata` of a Webset. Searches, imports, and enrichments are managed through their own endpoints.
POST /v0/websets/{id} - Destructive
Delete a Webset
Deletes a Webset. Once deleted, the Webset and all its Items will no longer be available.
DELETE /v0/websets/{id} - Destructive
Cancel a running Webset
Cancels all operations being performed on a Webset. Any enrichment or search will be stopped and the Webset will be marked as `idle`.
POST /v0/websets/{id}/cancel
Searches
- Read
Get a Search
Gets a Search by id
GET /v0/websets/{webset}/searches/{id} - Write
Create a Search
Creates a new Search for the Webset. The default behavior is to reuse the previous Search results and evaluate them against the new criteria.
POST /v0/websets/{webset}/searches - Destructive
Cancel a running Search
Cancels a currently running Search. You can cancel all searches at once by using the `websets/:webset/cancel` endpoint.
POST /v0/websets/{webset}/searches/{id}/cancel
Enrichments
- Read
Get an Enrichment
Returns an Enrichment configured on a Webset, including its status, description, format, and options.
GET /v0/websets/{webset}/enrichments/{id} - Write
Create an Enrichment
Create an Enrichment for a Webset.
POST /v0/websets/{webset}/enrichments - Write
Update an Enrichment
Update an Enrichment configuration for a Webset.
PATCH /v0/websets/{webset}/enrichments/{id} - Destructive
Delete an Enrichment
When deleting an Enrichment, any running enrichments will be canceled and all existing `enrichment_result` generated by this Enrichment will no longer be available.
DELETE /v0/websets/{webset}/enrichments/{id} - Destructive
Cancel a running Enrichment
All running enrichments will be canceled. You can not resume an Enrichment after it has been canceled.
POST /v0/websets/{webset}/enrichments/{id}/cancel
Items
- Read
Get an Item
Returns a Webset Item.
GET /v0/websets/{webset}/items/{id} - Read
List all Items for a Webset
Returns a list of Webset Items. You can paginate through the Items using the `cursor` parameter.
GET /v0/websets/{webset}/items - Destructive
Delete an Item
Deletes an Item from the Webset. This will cancel any enrichment process for it.
DELETE /v0/websets/{webset}/items/{id}
Websets Preview
- Read
Preview a webset
Returns how a search query will be interpreted before you create a Webset, including the detected entity, generated criteria, and suggested enrichments.
POST /v0/websets/preview
Monitors Runs
- Read
Webset list Monitor Runs
Lists all runs for the Monitor.
GET /v0/monitors/{monitor}/runs - Read
Webset get Monitor Run
Gets a specific monitor run.
GET /v0/monitors/{monitor}/runs/{id}
Imports
- Read
List Imports
Lists all imports for the Webset.
GET /v0/imports - Read
Get Import
Gets a specific import.
GET /v0/imports/{id} - Write
Create an Import
Creates an Import for your own data. Upload the file to the returned `uploadUrl` before `uploadValidUntil`, 1 hour after creation. Use an Import to enrich its records, to search within them with `scope`, or to leave them out of searches with `exclude`.
POST /v0/imports - Write
Update Import
Updates a import configuration.
PATCH /v0/imports/{id} - Destructive
Delete Import
Deletes a import.
DELETE /v0/imports/{id}
Webhooks
- Read
List webhooks
Returns the active Webhooks for your team. You can paginate through the results using the `cursor` parameter.
GET /v0/webhooks - Read
Get a Webhook
Returns a Webhook by id, including its status, subscribed events, target URL, and metadata. The signing `secret` is not returned.
GET /v0/webhooks/{id} - Write
Create a Webhook
Creates a Webhook that delivers the selected events to your URL as they occur. The response includes the signing `secret` used to verify deliveries; it is only returned on creation.
POST /v0/webhooks - Write
Update a Webhook
Updates the target URL, subscribed events, or metadata of a Webhook. Omitted fields are left unchanged.
PATCH /v0/webhooks/{id} - Destructive
Delete a Webhook
Deletes a Webhook. Its status becomes `inactive`, which stops future webhook deliveries to its URL.
DELETE /v0/webhooks/{id}
Webhooks Attempts
- Read
List webhook attempts
List all attempts made by a Webhook ordered in descending order.
GET /v0/webhooks/{id}/attempts
Events
- Read
List all Events
List all events that have occurred in the system. You can paginate through the results using the `cursor` parameter.
GET /v0/events - Read
Get an Event
Get a single Event by id. You can subscribe to Events by creating a Webhook.
GET /v0/events/{id}
Team Management service key (separate host)
- Read
List API keys
Returns the authenticated team's API keys. Pass `api_key_id` to return a single key.
GET /api-keys - Read
Get API key
Retrieves details of a specific API key by its ID.
GET /api-keys/{id} - Read
Get API key usage
Returns an API key's cost over a time period, in total and by price.
GET /api-keys/{id}/usage - Write
Create API key
Creates a new API key for the authenticated team. Optionally specify a name, rate limit, and budget for the API key.
POST /api-keys - Write
Update API key
Updates an existing API key's name and/or rate limit. Only API keys belonging to the authenticated team can be updated.
PUT /api-keys/{id} - Destructive
Delete API key
Deletes an API key. Only API keys belonging to the authenticated team can be deleted.
DELETE /api-keys/{id}
No operations match.
Get started
- Open Space settings → Connections and search for Exa.
- Connect your account and add the connection to the Space.
- Ask for what you need in any thread in that Space.
See How connections work for access and permissions, or browse all integrations.