Exa API 402 blocks Fed search

On September 8, 2026, a search request for “Federal Reserve September rate cut” failed before it returned any reporting. The only output was “Exa API returned 402,” which stopped article retrieval and left no source links to review. That meant the downstream system could not assemble a sourced briefing on the Federal Reserve query. Exa’s own documentation says HTTP 402 is used in its x402 payment flow for Search and Contents API access, while MDN describes 402 as a nonstandard “Payment Required” status code. ### Why did a Fed-related search end with no articles at all? The query string was “Federal Reserve September rate cut,” but the failure happened at the API layer, not at the topic layer. The returned error prevented the search system from receiving article metadata, URLs, or text, so there was nothing to cite or summarize. The upstream briefing for this story said the pre-fetched feed contained only failed searches and no usable articles or URLs. (exa.ai) That distinction matters operationally. A bad search result still produces records that can be filtered or discarded; a 402 response stops retrieval before results are delivered. In this case, the assistant’s refusal to produce a sourced briefing followed from the absence of source material, not from any judgment about the Federal Reserve topic itself. ### What does HTTP 402 mean here? MDN says HTTP 402 “Payment Required” is a nonstandard response code reserved for future use. In practice, modern APIs sometimes use it to signal a billing gate, quota problem, subscription issue, or pay-per-request requirement rather than a syntax error or missing endpoint. Exa’s documentation ties 402 directly to its x402 payment model. The company says clients can use Search and Contents without an API key by paying per request with USDC, and that the flow begins with a 402 response that tells the client to pay and retry. Exa lists `/search` and `/contents` as supported endpoints in that model. ### Does a 402 response always mean the account is out of money? (developer.mozilla.org) Exa’s public documentation does not say that every 402 response means the same thing. The docs describe 402 as part of an intentional payment protocol for certain request flows, which means the code can reflect a required payment handshake rather than a broken server. Third-party references on HTTP status codes say 402 is often used by APIs for billing restrictions, expired subscriptions, or quota controls, but those are general descriptions rather than Exa-specific statements. (exa.ai) Without the full response body, headers, or account configuration, it is not possible to say from the error string alone whether the failed Fed search stemmed from missing payment setup, a plan limit, or a client that did not handle Exa’s payment-required flow. ### Has this kind of Exa 402 failure shown up elsewhere? GitHub issues filed in February 2026 reported Exa-backed web search returning HTTP 402 in OpenCode, with users saying searches that had previously worked were failing without detailed response bodies. Those reports are not official Exa incident notices, but they show other developers have encountered the same status code in search workflows. (devtools.tools) Those issue reports also highlight a second problem visible in this case: thin error reporting. When a tool surfaces only “Request failed with status code 402,” users can see that billing or payment may be involved, but they still lack the request-specific detail needed to fix the call quickly. ### Why couldn’t the assistant just write around the failure? (github.com) The missing output was the source material. The upstream briefing said the system was required to use only the provided pre-fetched content and include citations, but the feed contained no article text and no URLs because the search failed. That left the assistant with a narrow factual basis: a named query, an Exa 402 error, and the absence of retrievable links. (github.com) Under those conditions, the only defensible response was to say a sourced briefing could not be produced. ### What should be checked next? Exa’s current documentation says `/search` can run under its x402 model, which requires a payment-and-retry flow for eligible requests. The practical next checks are the request mode being used, whether the client supports Exa’s 402 payment flow, whether billing or credits are configured correctly, and whether the response included headers or a request ID that can be used with Exa support. A successful rerun of the same “Federal Reserve September rate cut” query would need to return article URLs or content records before any sourced briefing could be written. (exa.ai)