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

# OpenAPI Specification

> Download the OpenAPI specs for the Exa public API and Team Management API in YAML or JSON.

***

You can view up-to-date versions of our OpenAPI specs here:

* Public API Spec: [YAML](https://exa.ai/docs/exa-spec.yaml) · [JSON](https://exa.ai/docs/exa-spec.json)
* [Team Management API Spec](https://exa.ai/docs/team-management-spec.yaml)

> [!NOTE]
>
> The raw OpenAPI specs are the source of truth for request and response schemas. Generated
> reference pages may omit recipes, migration notes, and recommended defaults; use the guides and
> examples for current integration guidance such as `type: "auto"`, highlights, and freshness
> settings. These links always point at the specs served by this docs deployment.