## TL;DR

Dont write one pagination reader for all SearchApi engines.

## Fix

1. Dont write one pagination reader for all SearchApi engines.
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this SearchApi bing engine feature.
- The symptom matches: pagination is current/next/other_pages, not next_page_token.

## When NOT to use

- Unrelated SearchApi bing engine issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against SearchApi bing engine.

## Variant phrasings

### pagination is current/next/other_pages, not next_page_token

## Why it happens

Official docs: the SearchApi Bing docs show a pagination shape different from the token pattern other engines use. Instead of next_page_token the pagination block returns current, a next URL, and an other_pages map of page numbers to URLs. Agents that blindly read pagination.next_page_token get nothing back and conclude there is only one page. Docs: https://www.searchapi.io/docs/bing

## 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.