> ## 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. # Get API key usage > Retrieve usage analytics and billing data for a specific API key. > [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. ## Important Notes * **Lookback Limit**: A `start_date` older than 180 days returns `400`. * **Zero Usage**: If the API key has no usage in the requested period, `total_cost_usd` will be 0 and `cost_breakdown` may be empty. * **Team Ownership**: The service API key used for authentication must belong to the same team as the requested API key. Cross-team access is not permitted. * **Date Formats**: Dates can be provided in ISO 8601 format with or without time components (e.g., `2025-01-01` or `2025-01-01T00:00:00Z`). ## OpenAPI ````yaml team-management-spec.yaml GET /api-keys/{id}/usage 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/{id}/usage: get: tags: - Team Management summary: Get API key usage description: Returns an API key's cost over a time period, in total and by price. operationId: get-api-key-usage parameters: - name: id in: path required: true schema: type: string description: >- The key's `publicId`. The key's current secret is also accepted for backward compatibility. - name: start_date in: query required: false schema: type: string format: date-time description: >- Start date for the usage period (ISO 8601 format). Defaults to 30 days ago. Must be within the last 6 months (180 days). example: '2025-01-01T00:00:00Z' - name: end_date in: query required: false schema: type: string format: date-time description: >- End date for the usage period (ISO 8601 format). Defaults to current time. example: '2025-01-31T23:59:59Z' - name: group_by in: query required: false schema: type: string enum: - hour - day - month description: Has no effect on the response. example: day responses: '200': description: Usage data retrieved successfully content: application/json: schema: type: object properties: id: type: string description: The key's `publicId`, its stable identifier. api_key_id: type: string format: uuid description: >- The API key's secret, kept for backward compatibility. Despite the field name it is not an identifier; use `id` to identify the key. api_key_name: type: - string - 'null' description: The name of the API key team_id: type: string format: uuid description: The team ID this key belongs to period: type: object properties: start: type: string format: date-time description: Start of the usage period end: type: string format: date-time description: End of the usage period total_cost_usd: type: number description: Total cost in USD for the period example: 45.67 cost_breakdown: type: array description: Breakdown of costs by price type items: type: object properties: price_id: type: string description: Unique identifier for the price price_name: type: string description: >- Name of the price (e.g., "Neural Search", "Content Retrieval") quantity: type: number description: Total quantity consumed amount_usd: type: number description: Cost in USD for this price type metadata: type: object properties: generated_at: type: string format: date-time description: When this report was generated example: id: key_abc123def456 api_key_id: 550e8400-e29b-41d4-a716-446655440000 api_key_name: Production API Key team_id: 660e8400-e29b-41d4-a716-446655440000 period: start: '2025-01-01T00:00:00Z' end: '2025-01-31T23:59:59Z' total_cost_usd: 45.67 cost_breakdown: - price_id: price_neural_search price_name: Neural Search quantity: 1000 amount_usd: 30 - price_id: price_content_retrieval price_name: Content Retrieval quantity: 500 amount_usd: 15.67 metadata: generated_at: '2025-02-01T10:30:00Z' '400': description: Bad Request - Invalid parameters content: application/json: schema: type: object properties: error: type: string examples: - Invalid API key ID format. - >- Invalid date format. Use ISO 8601 format (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss) - start_date must be before end_date - >- Date range too far in the past. start_date must be within the last 6 months. - >- Invalid group_by parameter. Must be one of: hour, day, month '401': description: Unauthorized - Invalid or missing service key content: application/json: schema: type: object properties: error: type: string example: Unauthorized '404': description: Not Found - API key does not exist content: application/json: schema: type: object properties: error: type: string example: API key not found '500': description: Internal Server Error - Failed to fetch usage data content: application/json: schema: type: object properties: error: type: string example: Failed to fetch usage data. Please try again later. security: - apikey: [] x-codeSamples: - lang: bash label: Get usage for the last 30 days (default) source: > curl -X GET 'https://admin-api.exa.ai/team-management/api-keys/{id}/usage' \ -H 'x-api-key: YOUR-SERVICE-KEY' - lang: bash label: Get usage for a specific date range source: > curl -X GET 'https://admin-api.exa.ai/team-management/api-keys/{id}/usage?start_date=2025-01-01&end_date=2025-01-31' \ -H 'x-api-key: YOUR-SERVICE-KEY' - lang: python label: Get usage for a specific date range source: | import requests from datetime import datetime, timedelta headers = { 'x-api-key': 'YOUR-SERVICE-KEY' } params = { 'start_date': '2025-01-01T00:00:00Z', 'end_date': '2025-01-31T23:59:59Z' } response = requests.get( 'https://admin-api.exa.ai/team-management/api-keys/{id}/usage', headers=headers, params=params ) print(response.json()) - lang: javascript label: Get usage for a specific date range source: | const params = new URLSearchParams({ start_date: '2025-01-01T00:00:00Z', end_date: '2025-01-31T23:59:59Z' }); const response = await fetch( `https://admin-api.exa.ai/team-management/api-keys/{id}/usage?${params}`, { 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 ````