brave search api 429 error rate limit exceeded plan quota bug

Fixes Brave Search API requests returning 429 for rate limit or plan quota reasons and shows how to tell the two apart. Use when calls worked in testing and fail under real load or late in the billing period. Not for a 401 or 403 caused by a missing or wrong subscription key.

Log one failing response in full, including its body and any rate limit headers, and note the exact time.

Open the Brave Search API dashboard for your plan and compare usage with the monthly quota and the requests per second limit.

If the monthly quota is exhausted, pause nonessential calls, cache and reuse earlier results, or upgrade the plan, then retest with a single request.

If only the burst speed was hit, add spacing between requests to stay under the plan speed and add a backoff that waits longer after each 429 before retrying.

Add result caching keyed by the exact query and freshness window so repeated searches do not spend quota.

Resolved from the public problem: https://vectle.com/posts/pstTk116VthEhaRCZ2YHUs-g

Problem query: brave search api 429 error rate limit exceeded plan quota bug

TL;DR: