YouTube API 402 error stopped two searches

Exa-linked searches for two YouTube topics failed on May 23 with the same 402 error, leaving no usable result set for recent coverage of Phnom Penh tourism and Bitcoin regulation. The failures were recorded in media checks covering the May 23-24 window. The error message cited in both cases was “Exa API returned 402,” according to the source briefing. The result was a gap in recent video discovery for both topics and no usable YouTube-based thread to summarize from those searches. ### Which searches failed, and when did they fail? The two failed queries were YouTube searches for Phnom Penh tourism and Bitcoin regulation, according to the media briefing prepared on Sunday, May 24. The note said the API issue was flagged on May 23 and affected searches run over the last 48 hours. The Phnom Penh query was described as a YouTube search for Cambodia tourism coverage, while the second was a YouTube search for Bitcoin regulation podcast or video coverage. In both cases, the reported outcome was the same: no usable YouTube results were returned because the search pipeline stopped at a 402 error. ### What does a 402 error point to in this case? Exa’s documentation says its `/search` and `/contents` endpoints can return HTTP 402 Payment Required when a request is sent without an API key or payment header. Exa says those endpoints support an x402 payment flow and that requests without the required credentials can trigger that response. Exa’s quickstart and API reference also say standard access can be provided through an API key passed in the request headers. The company says API-key billing and x402 payment are separate paths, and that normal API-key billing takes priority when a valid key is included. ### Was this a YouTube platform outage? Google’s YouTube Data API documentation says requests must include either an API key or an OAuth 2.0 token, and it separately documents quota systems and API error classes for YouTube requests. (exa.ai) Google’s published materials do not describe “Exa API returned 402” as a native YouTube error string. Google also says YouTube Data API projects receive a default daily quota allocation of 10,000 units, and that search requests consume quota under that system. (exa.ai) Google’s quota troubleshooting materials say quota overruns commonly surface as 403 quota-related errors, not 402 payment-required responses. ### What was the practical effect on coverage? The immediate effect was a missing slice of recent media monitoring. (developers.google.com) The Phnom Penh tourism search produced no usable YouTube results, and the related podcast returns in the source briefing were described as unrelated to Cambodia, making them unusable as substitutes. The Bitcoin regulation search also produced no usable YouTube result set in the source material. That left the media note with a documented discovery gap rather than a content summary. (developers.google.com) In practice, the failure meant there was no verified list of recent YouTube videos or podcasts from May 23-24 to assess for either topic. ### What can be verified from the underlying services? Exa says its search product is a web search API and documents both API-key access and x402-based payment handling on its search endpoints. Google says the YouTube Data API remains the underlying interface for searching YouTube content and requires credentials and quota management for access. May 24 is the latest dated briefing point for this incident in the source material. Exa’s documentation pages and Google’s YouTube API reference remain the named places to check for the next update on credentials, quota handling, or error behavior. (docs.exa.ai) (exa.ai)