> ## 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. > 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. # Get a run > Retrieves a single run by its ID, including the full output if the run is completed. ## OpenAPI ````yaml exa-spec.yaml GET /monitors/{id}/runs/{runId} openapi: 3.1.0 info: title: Exa Public API version: 2.0.0 servers: - url: https://api.exa.ai security: - apiKey: [] - bearer: [] paths: /monitors/{id}/runs/{runId}: get: tags: - Runs summary: Get a run description: >- Retrieves a single run by its ID, including the full output if the run is completed. operationId: getRun parameters: - in: path name: id schema: type: string description: The monitor ID required: true description: The monitor ID - in: path name: runId schema: type: string description: The run ID required: true description: The run ID responses: '200': description: The run headers: x-request-id: $ref: '#/components/headers/XRequestId' content: application/json: schema: $ref: '#/components/schemas/SearchMonitorRun' '400': $ref: '#/components/responses/BadRequestResponse' '401': $ref: '#/components/responses/UnauthorizedResponse' '403': $ref: '#/components/responses/ForbiddenResponse' '404': $ref: '#/components/responses/NotFoundResponse' '500': $ref: '#/components/responses/InternalServerErrorResponse' x-codeSamples: - lang: bash source: |- curl -X GET https://api.exa.ai/monitors//runs/ \ -H "x-api-key: $EXA_API_KEY" - lang: javascript source: |- import Exa from "exa-js"; const exa = new Exa(process.env.EXA_API_KEY); const result = await exa.monitors.runs.get("", ""); - lang: python source: |- from exa_py import Exa exa = Exa(api_key="YOUR_API_KEY") result = exa.monitors.runs.get("", "") components: headers: XRequestId: description: >- Unique identifier for the request. Matches the `requestId` field returned in response bodies that carry one. schema: type: string schemas: SearchMonitorRun: type: object properties: id: type: string description: The unique identifier for the run monitorId: type: string description: The monitor this run belongs to status: type: string enum: - pending - running - completed - failed - cancelled description: The status of the run output: anyOf: - $ref: '#/components/schemas/SearchMonitorRunOutput' - type: 'null' description: The output of the run. Null until the run completes. failReason: anyOf: - type: string enum: - api_key_invalid - insufficient_credits - invalid_params - rate_limited - source_not_available - forbidden - search_unavailable - search_failed - internal_error - type: 'null' description: >- The reason the run failed. Null unless status is `failed`. `source_not_available` means the search requested a domain Exa cannot return (remove it from the search), and `forbidden` means the request was otherwise not permitted. startedAt: anyOf: - type: string format: date-time - type: 'null' description: When the run started executing format: date-time completedAt: anyOf: - type: string format: date-time - type: 'null' description: When the run completed successfully format: date-time failedAt: anyOf: - type: string format: date-time - type: 'null' description: When the run failed format: date-time cancelledAt: anyOf: - type: string format: date-time - type: 'null' description: When the run was cancelled format: date-time durationMs: anyOf: - type: integer - type: 'null' description: Total execution time in milliseconds createdAt: type: string format: date-time description: When the run was created updatedAt: type: string format: date-time description: When the run was last updated required: - id - monitorId - status - output - failReason - startedAt - completedAt - failedAt - cancelledAt - durationMs - createdAt - updatedAt additionalProperties: false SearchMonitorRunOutput: type: object properties: results: anyOf: - type: array items: type: object propertyNames: type: string additionalProperties: $ref: '#/components/schemas/JsonValue' - type: 'null' description: The search results content: description: >- Synthesized content from the search results. Shape depends on `outputSchema.type`. oneOf: - $ref: '#/components/schemas/JsonValue' - type: 'null' grounding: anyOf: - type: array items: type: object properties: field: type: string description: The output field this citation applies to citations: type: array items: type: object properties: url: type: string format: uri description: Source URL. title: type: string description: Source title. required: - url - title additionalProperties: false confidence: type: string enum: - low - medium - high description: Model-reported reliability for this field. required: - field - citations - confidence additionalProperties: false - type: 'null' description: Field-level citations with confidence levels 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. JsonValue: description: Any JSON value. oneOf: - type: 'null' - type: boolean - type: number - type: string - type: array items: $ref: '#/components/schemas/JsonValue' - type: object propertyNames: type: string additionalProperties: $ref: '#/components/schemas/JsonValue' 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' NotFoundResponse: description: The requested resource does not exist. 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 . ````