Team reruns prefetches after Exa API outage broke three overnight news searches

The overnight workflow failed before any briefing could be written. A source bundle reviewed for September 2, 2026 said three pre-fetched news searches returned HTTP 402 errors during prefetching, leaving no article text, excerpts or in-bundle links to support a 600-to-800 word news brief. The failed topics were listed as “Ukraine drone strikes Russia,” “China property stimulus measures,” and “Nvidia antitrust probe AI.” The bundle said that, under the workflow’s rules, the assistant could use only pre-fetched material and had to cite key claims from the supplied sources. With no fetched articles in the package, it said, the only supported factual claim was that the searches failed. ### Which searches broke in the overnight run? Three named topics were affected in the run described in the bundle: “Ukraine drone strikes Russia,” “China property stimulus measures,” and “Nvidia antitrust probe AI.” The briefing said each search failed at the same stage — prefetching — and each came back with an HTTP 402 response. Those labels matter because they define the outer limit of what can be reported from the package. The bundle explicitly said it did not provide verifiable reporting on any fresh Ukrainian drone campaign against Russia, any new Chinese property-sector support measures, or any antitrust development involving Nvidia and artificial intelligence. ### What does an HTTP 402 response mean here? Exa’s documentation says the company supports 402 responses on its `/search` and `/contents` endpoints when a request arrives without an API key or payment header, and that the response includes payment details in a `PAYMENT-REQUIRED` header. Exa’s pricing page says the service is pay-as-you-go and funded through credits rather than a fixed subscription. MDN describes HTTP 402 as a nonstandard “Payment Required” client-error status code reserved for future use in digital payment systems. In practice, companies can implement it differently, but the common thread is that the requested resource is not being served until a payment condition is met. ### Why couldn’t the system just write around the outage? The workflow described in the bundle barred that option. (exa.ai) The source note said the assistant had to rely only on pre-fetched news content already inside the package and include source citations for key claims. Without article bodies, excerpts or URLs, any attempt to summarize the three topics would have required adding facts not present in the supplied material. That left the process with a narrow, documentable outcome: the retrieval layer failed. (developer.mozilla.org) The bundle also said retrieval-failure themes had appeared in prior briefings and that repeating them would have conflicted with instructions not to revisit already covered stories. ### Did Exa report a broader outage? Exa’s public status page showed an incident on August 25, 2026 involving elevated latency in the `/search` endpoint, but the status results reviewed did not show a matching public incident for the September 2 overnight run described in the bundle. That does not rule out an account-level billing issue, a configuration problem or an unposted incident; it means only that the public status page, as reviewed, did not independently confirm this specific failure. That distinction matters because a 402 response points first to access or payment conditions, not necessarily to a platform-wide outage. The bundle itself did not claim a systemwide Exa disruption. It said only that the three searches returned 402 errors during prefetching. ### What was the proposed fix? The bundle gave two concrete next steps: rerun the failed prefetches, or paste in the relevant article URLs or text so the assistant can work from usable source material. (status.exa.ai) That is consistent with the workflow it described, because either step would restore the missing inputs — fetched content and citable links. The next observable milestone is a successful rerun of the three named searches or a replacement source pack containing article text and URLs for the Ukraine, China and Nvidia topics. Until one of those inputs appears, the record supports only the failed prefetches and the three HTTP 402 responses.