Exa Latency and Retrieval Performance Tuning

Overview

Tune Exa search type, content mode, freshness, result count, and concurrency against measured latency and retrieval quality. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries.

Prerequisites

• The target repository, environment, Exa team, product surface, and accountable owner.
• The workload's data classification, latency and freshness promise, cost ceiling, and retention policy.
• Current first-party documentation plus credentials only for a narrowly approved live check.

Current Contract

Search types trade latency and synthesis depth; content extraction, outputSchema, forced livecrawl, summaries, and subpages add work. Highlights are usually more token-efficient than full text. Published latency values are guidance, not a service-specific SLO.

Authentication

For normal REST work, inject EXA_API_KEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client.