> ## 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. # List API keys > Retrieve all API keys belonging to your team with their metadata. > [card] [Get your Exa API key](https://dashboard.exa.ai/api-keys?utm_source=docs\&utm_medium=docs\&utm_campaign=get_key_card) > > Create a key in the dashboard. New accounts start with free credits. > [!NOTE] > > The Team Management API is enabled per team. It authenticates with a service account API key, which is created from the **Service keys** tab on the [API keys page](https://dashboard.exa.ai/api-keys?utm_source=docs\&utm_medium=docs\&utm_campaign=team_management_access) once the feature is enabled for your team. Contact [support@exa.ai](mailto:support@exa.ai) to request access. ## OpenAPI ````yaml team-management-spec.yaml GET /api-keys openapi: 3.1.0 info: version: 1.0.0 title: Team Management API description: >- API for managing API keys within teams. Provides CRUD operations for creating, listing, updating, and deleting API keys with team-based access controls. The API is enabled per team. Contact support@exa.ai to request access. servers: - url: https://admin-api.exa.ai/team-management security: - apikey: [] paths: /api-keys: get: tags: - Team Management summary: List API keys description: >- Returns the authenticated team's API keys. Pass `api_key_id` to return a single key. operationId: list-api-keys parameters: - name: api_key_id in: query required: false schema: type: string description: >- Optional `publicId` of a single key to return. The key's current secret is also accepted for backward compatibility. responses: '200': description: List of API keys retrieved successfully content: application/json: schema: oneOf: - type: object properties: apiKeys: type: array items: type: object properties: id: type: string format: uuid description: >- The API key's secret. Despite the field name it is not an identifier; use `publicId` to identify the key. publicId: type: string description: >- Stable identifier of the API key. It does not change when the key is rotated. name: type: string rateLimit: type: - integer - 'null' description: Rate limit in requests per second budgetCents: type: - integer - 'null' description: >- Spending budget for the API key in the team's current billing period, in cents isOverBudget: type: boolean description: Whether the API key is currently over its budget previousSecretExpiresAt: type: - string - 'null' format: date-time description: >- When the secret replaced by the last rotation stops working, or null if it no longer works. - type: object properties: apiKey: type: object properties: id: type: string format: uuid description: >- The API key's secret. Despite the field name it is not an identifier; use `publicId` to identify the key. publicId: type: string description: >- Stable identifier of the API key. It does not change when the key is rotated. name: type: string rateLimit: type: - integer - 'null' description: Rate limit in requests per second budgetCents: type: - integer - 'null' description: >- Spending budget for the API key in the team's current billing period, in cents isOverBudget: type: boolean description: Whether the API key is currently over its budget teamId: type: string format: uuid createdAt: type: string format: date-time '400': description: Bad request - invalid API key ID format content: application/json: schema: type: object properties: error: type: string example: Invalid API key ID format. '401': description: Unauthorized - Invalid or missing service key content: application/json: schema: type: object properties: error: type: string example: Unauthorized '403': description: Forbidden - insufficient permissions to access this API key content: application/json: schema: type: object properties: error: type: string example: Insufficient permissions to access this API key '404': description: Not found - API key or team not found content: application/json: schema: type: object properties: error: type: string examples: - API key not found - Team not found security: - apikey: [] x-codeSamples: - lang: bash label: List all API keys source: | curl -X GET 'https://admin-api.exa.ai/team-management/api-keys' \ -H 'x-api-key: YOUR-SERVICE-KEY' - lang: python label: List all API keys source: | import requests headers = { 'x-api-key': 'YOUR-SERVICE-KEY' } response = requests.get( 'https://admin-api.exa.ai/team-management/api-keys', headers=headers ) print(response.json()) - lang: javascript label: List all API keys source: > const response = await fetch('https://admin-api.exa.ai/team-management/api-keys', { method: 'GET', headers: { 'x-api-key': 'YOUR-SERVICE-KEY' } }); const result = await response.json(); console.log(result); components: securitySchemes: apikey: type: apiKey in: header name: x-api-key description: Service API key for team authentication ````