Exa API returned 402 errors

Exa’s own documentation indicates that HTTP 402 can appear in its ecosystem as a payment-related response, while the failed news pull described here produced no usable articles for three requested topics on September 7. The missing material covered Ukraine-Russia peace talks, China property stimulus and the economy, and U.S. election campaign polls. Without retrievable articles, there is no source base to support a reported briefing on those subjects. The immediate issue is not the underlying news events, but the broken retrieval layer that was supposed to supply them. ### Why would an “Exa API returned 402” message stop a news brief cold? HTTP 402 is defined by MDN as a “Payment Required” client error status, and MDN says it remains a nonstandard status code reserved for future use. In practice, that means a system can surface 402 when access depends on payment logic rather than on a normal successful fetch. Exa’s documentation says its x402 flow lets clients pay per request for certain endpoints and is built on the HTTP 402 status code. (exa.ai) Exa says the supported endpoints in that payment flow are `/search` and `/contents`, which are the kinds of endpoints a pipeline might rely on to retrieve source links or page text. ### What does Exa say about billing and credits? Exa says its API runs on a pay-as-you-go credit system, with usage charged against a credit balance visible in the billing dashboard. (developer.mozilla.org) The company says requests are billed according to published pricing or an enterprise contract. Exa’s pricing page says there is no subscription or minimum spend, that new accounts get $20 in free credits, and that the free tier adds $10 in credits each month. The same page lists Search at $7 per 1,000 requests and Contents at $1 per 1,000 pages per content type. (exa.ai) ### Does a 402 error prove the account ran out of money? Exa’s public pages reviewed here do not say that every 402 response means an account balance hit zero. MDN’s description is broader and says 402 is a nonstandard payment-related code, while Exa’s x402 guide presents it as part of a pay-and-retry flow for request-level access. (exa.ai) That leaves several possibilities that cannot be resolved from the error label alone. A 402 could reflect missing credits, a payment-gated request path, or another billing configuration issue, but that inference would require logs or dashboard evidence not provided in the failed feed. (exa.ai) ### Why did the failure matter for these three topics in particular? The reported failure mattered because all three requested coverage areas depended on prefetched source material that never arrived in usable form. (exa.ai) With no retrievable articles on the peace talks, China’s economy, or U.S. campaign polling, any substantive write-up would require importing outside reporting rather than using the supplied material. That would change the assignment from synthesis to fresh reporting. A news brief built on missing links also cannot meet normal sourcing standards. If the retrieval layer returns only error strings instead of URLs, headlines, or article text, there is nothing to quote, attribute, or verify against the original publication. ### What should be checked before trying the pull again? Exa’s billing page says remaining balance is visible in the dashboard, and its pricing and rate-limit pages separate billing issues from throughput limits such as queries per second. (exa.ai) That means the first checks are whether credits are available, whether the request path used a payment-gated endpoint, and whether the fetch process captured the underlying response body rather than only a generic error label. The practical next step is straightforward. A refreshed run should resend working article URLs or a new prefetched bundle with retrievable source text for the three requested topics, after which the briefing can be rebuilt from those materials. (exa.ai)