100 tasks per POST 2000 calls per minute

Not specified by the original author.

TL;DR

Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. The practical consequence: chunk keyword lists into groups of 100 per POST and throttle to stay under the per-minute ceiling.

Steps

1. Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. The practical consequence: chunk keyword lists into groups of 100 per POST and throttle to stay under the per-minute ceiling. Oversized batches do not queue gracefully - split them client-side before sending.

When to use

You are seeing this: Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. Use this skill when you run into "100 tasks per POST, 2000 calls per minute - chunk batches client-side".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: DataForSEO field notes (dataforseo-brain SERP API concept page): hard throughput limits - up to 2000 combined POST + GET calls per minute, max 100 tasks per POST, keyword capped at 700 chars, depth capped at 200.

Verified resolution: Design your batching around the caps: 100 tasks max per POST, 2000 total calls per minute, keywords truncated at 700 characters, depth at 200. The practical consequence: chunk keyword lists into groups of 100 per POST and throttle to stay under the per-minute ceiling. Oversized batches do not queue gracefully - split them client-side before sending.

Source URL: https://github.com/agricidaniel/dataforseo-brain/blob/HEAD/wiki/concepts/cap-serp-api.md

Not specified by the original author.

Brave Search API free tier: 1 req/sec, so serialize calls and retry 429s

TL;DR

Brave Search API free tier: 1 request/second, 2,000/month. Treat these as hard rules: - Never run searches in parallel. One query at a time; refine from the result before issuing the next.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

• A 429 on the free plan usually means you exceeded 1 rps, not that the monthly quota is gone. Sleep ~1.1s and retry with backoff instead of declaring the key dead. - Use a cross-process lock if multiple processes or threads can search, so pacing holds globally. - Log the remaining monthly quota (response header X-RateLimit-Remaining) after each call. Read that line before concluding the key is exhausted. - If 429s survive retries, the month's quota is spent; wait for the reset or upgrade rather than hammering. Rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are your pacing source of truth; use X-RateLimit-Reset for the backoff instead of guessing.

Context: Web (agent-config brave-search SKILL.md): the Brave Search API free plan allows 1 request per second and 2,000 requests per month. The documented rule: never issue calls in parallel; one query at a time. The reference implementation paces requests through a cross-process lock and retries 429 with backoff, so concurrent invocations serialize to ~1.1s apiece instead of failing. Every run prints the remaining monthly quota (e.g. "monthly quota remaining: 1965/2000"); read that line before concluding the key is exhausted, because a 429 at 1 rps is pacing, not quota exhaustion.

Source: Web (agent-config brave-search SKILL.md): the Brave Search API free plan allows 1 request per second and 2,000 requests per month. The documented rule: never issue calls in parallel; one query at a time. The reference implementation paces requests through a cross-process lock and retries 429 with backoff, so concurrent invocations serialize to ~1.1s apiece instead of failing. Every run prints the remaining monthly quota (e.g. "monthly quota remaining: 1965/2000"); read that line before concluding the key is exhausted, because a 429 at 1 rps is pacing, not quota exhaustion.

Verified resolution: Brave Search API free tier: 1 request/second, 2,000/month. Treat these as hard rules: - Never run searches in parallel. One query at a time; refine from the result before issuing the next. - A 429 on the free plan usually means you exceeded 1 rps, not that the monthly quota is gone. Sleep ~1.1s and retry with backoff instead of declaring the key dead. - Use a cross-process lock if multiple processes or threads can search, so pacing holds globally. - Log the remaining monthly quota (response header X-RateLimit-Remaining) after each call. Read that line before concluding the key is exhausted. - If 429s survive retries, the month's quota is spent; wait for the reset or upgrade rather than hammering. Rate-limit headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset) are your pacing source of truth; use X-RateLimit-Reset for the backoff instead of guessing.

Source URL: https://github.com/junghan0611/agent-config/blob/HEAD/skills/brave-search/SKILL.md

Not specified by the original author.

TL;DR

There is no fixed monthly query count on the Brave Search API free plan anymore. The free plan gives you $5 in free credits each month, auto-applied to your account, and the number of queries that buys depends on which endpoints you call, because Search, Answers, and the other endpoints each bill at a different rate per 1,000 requests. A card is required to sign up, as an identity check only, and it is not charged while you stay inside the free credits.

brave search api free plan monthly queries

The short version: monthly queries = $5 of credits divided by the per-request price of the endpoints you use. Anyone quoting you one flat number is reading an old guide.

Use this when

• You are estimating cost before integrating the Brave Search API
• A guide, blog post, or skill file quotes a flat number of free Brave queries per month and you want to know if it is still true
• You signed up for the free plan and the dashboard shows credits instead of a query quota
• You want to stay inside the free tier and need to know what actually stops the card being charged

Not for this skill when

• You need the exact per-endpoint price for a paid plan (read the pricing on the Brave Search API page; rates differ per endpoint and change over time)
• You are hitting 429 rate limit errors on the free tier (that is a requests-per-second pacing problem, see the related skills below)
• You need storage rights for results, for example to train a model (the free credits do not grant that; it needs a plan that explicitly includes storage)

Steps

1. Sign up on the Brave Search API page and choose the free option. Add a card when asked; it is an identity check, not a purchase.

Expected: your account is created with $5 in free credits showing for the current month.

2. Work out your real monthly query count from the endpoints you will call. Check the rate per 1,000 requests for each endpoint you plan to use (Search, Answers, and the rest bill differently), then divide the $5 credit by that rate. A workload that only calls the cheapest endpoint gets far more monthly queries than one built on a pricier endpoint.

Expected: you have a per-endpoint estimate, not a single magic number. If your estimate and a third-party guide disagree, the guide is probably quoting the old flat tier.

3. Take your key from the API dashboard and call the API at api.search.brave.com, sending your subscription token in the request header.

Expected: calls succeed and draw down the monthly credits shown in the dashboard.

4. Watch usage in the dashboard and set a usage limit there, so anything past the free credits cannot bill the card.

Expected: when the credits run out, calls stop or are capped by your limit instead of silently charging the card.

Variant phrasings

brave search api pricing free tier

Same answer: the free tier is credits now, not a quota. $5 a month, auto-applied, priced per endpoint.

brave api free queries per month

There is no plan-level number to quote. Do the step 2 math for your endpoint mix; that is the only honest answer.

brave search api cost

Past the free credits, cost is per 1,000 requests at the rate for each endpoint you call. The free plan is the $5 monthly credit described above; paid usage bills the card on the account.

is the old 2,000 free queries a month tier still available

No. That flat tier ended and credits replaced it, which is the root cause of most of the confusion around this query (see below).

Why the answer changed

Brave changed the Search API free tier: the old flat free tier, which older guides still quote as a fixed number of free queries a month, ended, and monthly credits replaced it. Third-party guides, blog posts, and skill files written against the old tier keep repeating the old number, so search results disagree with the dashboard. Trust the dashboard and the pricing page over any guide that names a flat monthly query count.

Edge cases

• The free credits reset monthly and do not roll over; unused credit at month end is lost.
• A card is required even for the free plan. It is an anti-fraud identity check and is not charged while you stay inside the credits, but an account with no card cannot sign up.
• Mixing endpoints makes the math fuzzy: a month of cheap Search calls plus a few expensive Answers calls drains credits faster than either rate alone suggests. Track the dashboard, not a spreadsheet.
• Storing results (for example to train a model) needs a plan that explicitly grants storage rights; spending free credits on calls does not grant them.

Tool compatibility

Brave Search API, free plan as described on the Brave Search API page (checked against the source below). Endpoint rates are per 1,000 requests and can change; re-check the pricing page before budgeting a paid workload.

Related skills

• brave search api 429 rate limit exceeded: https://vectle.com/skills/skli5O4nSJrQSHRYWOBk4gGQ
• Brave Search API free tier: 1 req/sec, so serialize calls and retry 429s: https://vectle.com/skills/skl_OdqKm7Bab9TiN4A5j8fGRQ

Provenance

Built from the Brave Search API page: the free offer is now $5 in credits applied automatically every month, with a card required at signup as an identity check.

Source: Brave changed the Search API free tier. Older guides still quote a flat 2,000 free queries a month, but that tier is gone. The current free offer is $5 in credits applied to your account automatically every month. A credit card is required at signup as an anti-fraud identity check, but it is not charged while you stay inside the free credits.

Verified resolution: There is no fixed monthly query count on the free plan anymore. You get $5 in free credits each month, auto-applied, and Search, Answers, and the other endpoints bill at different rates per 1,000 requests, so the query count depends on the endpoint mix. Sign up on the Brave Search API page, set a usage limit in the dashboard so usage past the credits cannot bill the card, and note the credits reset monthly and do not roll over.

Source URL: https://brave.com/search/api/