Exa blocks world briefing

Exa’s documentation points to a simple explanation for a search feed that returned only HTTP 402 errors: the company uses 402 Payment Required as part of its billing and access flow on core API endpoints. Exa says its Search and Contents APIs can answer a request with a 402 response when a client sends no API key or payment credential, and its billing page says requests are also blocked when an account’s credit balance runs out. That matters for any newsroom or research workflow that depends on pre-fetched search results. If the upstream fetcher is not authenticated, is using a payment-on-request setup it does not complete, or has exhausted prepaid credits, the result may be an empty packet rather than usable reporting. Exa’s public pricing and billing materials describe a pay-as-you-go credit model, not an unlimited search feed. (exa.ai) ### Why would Exa return a 402 instead of search results? Exa’s x402 guide says the company supports a payment flow built on HTTP 402 Payment Required for its `/search` and `/contents` endpoints. In that setup, a request sent without an API key or payment header gets a 402 response containing pricing details and supported payment networks, after which the client is expected to pay and retry. Exa’s MPP documentation describes a similar pattern. (exa.ai) It says the server responds with 402 and a payment challenge when a request arrives without an API key or payment credential. That means a 402 can be part of the normal protocol, not necessarily a server outage. ### Could a newsroom hit the same error with an API key? Exa’s billing documentation says yes. The company says API usage is funded through prepaid credits and that requests are blocked when the credit balance runs out, unless the user adds more credits or enables auto-recharge. (exa.ai) Exa’s pricing page says the platform is pay-as-you-go, with no subscription minimum, and that users are charged per request across products including Search and Contents. (exa.ai) The same page says new accounts receive $20 in free credits and free-tier accounts receive $10 in credits each month. ### What does that tell us about an empty pre-fetched briefing pack? Three failed searches by themselves do not verify anything about the underlying news topics. (exa.ai) A packet that contains only 402 errors shows a fetch failure at the search layer; it does not establish whether there were or were not real developments in politics, Federal Reserve signaling, or the war in Ukraine. That is an inference from Exa’s billing and payment design, not a statement Exa makes in those words. (exa.ai) Exa’s Search API materials describe the endpoint as a web search tool that can extract contents from results. If the search call never completes because access is blocked, the downstream briefing will have no article URLs or text to cite. ### What should the operator check first? Exa’s billing page says the remaining balance is visible on the Billing page and that users can manage credits, auto-recharge, receipts and invoices there. (exa.ai) That is the first place to check if a previously working pipeline suddenly starts returning blocked requests. The pricing page lists the current per-request rates for Search and Contents, while the x402 and MPP guides describe the alternative payment flows for clients that do not use standard API-key billing. (exa.ai) Together, those pages show the three practical failure points: no valid API key, no completed payment challenge, or no remaining credits. ### What happens next if the feed has already failed? A refreshed fetch is the next concrete step. (exa.ai) Exa’s documentation says blocked requests resume once credits are added or the payment flow is completed, and its billing tools expose usage and balance information tied to an API key. A rerun after those checks should determine whether the missing briefing was a payment problem or a separate issue in the fetch pipeline. (exa.ai)