## TL;DR

Paginate Brave Search results correctly: - count: 1-20, max 20 results per page (default 10). - offset: counts PAGES (0-9), not results. If your "page 2" looks identical to page 1, you are passing a result offset instead of a page offset. Results 21-40 = count=20&offset=1.

## Fix

1. Paginate Brave Search results correctly: - count: 1-20, max 20 results per page (default 10). - offset: counts PAGES (0-9), not results.
   Expected: You get the expected result; the problem is gone.
2. If your "page 2" looks identical to page 1, you are passing a result offset instead of a page offset.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Brave Search API offset counts pages, not results feature.
- The symptom matches: count=20&offset=1 for results 21-40.

## When NOT to use

- Unrelated Brave Search API offset counts pages, not results issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Brave Search API offset counts pages, not results.

## Variant phrasings

### count=20&offset=1 for results 21-40

## Why it happens

Web (draw-things-community WebSearch README): Brave supports at most 20 results per page and up to ten pages, and the page size stays fixed across requests because offset counts pages, not results. So to fetch results 21-40 you set count=20 and offset=1, not offset=20. A separate feasibility study notes that keyless results and pagination work but rapid sequential searches can require interactive verification, and HTTP errors are surfaced without retries. Agents that treat offset as a result offset silently re-fetch page one.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.