Skip to main content
Ask for page 2 of a search. Paging needs an API key.
One call returns one page, the way the site shows it. Page 2 continues page 1 with no repeats. A page holds what the site puts on it, so the number of results changes from call to call. Each endpoint pages in one of three ways. Its page in the API reference says which. Keep the rest of the input the same between pages. Each page is a normal call and costs its normal price.

Loop through numbered pages

Loop through cursors

The response carries a cursor when there is a next page. Send it back, unchanged, with the same input.
Set your own stop, like the 5 pages or 100 results above. Some sources have many pages. A cursor only works with the input that produced it. Any other cursor returns a 400 with code invalidRequest.

Keep fewer results

google.images, google.ads.advertisers, appstore.search, appstore.top and google.play.search take limit. Send it to return fewer results. On google.images, appstore.search, appstore.top and google.play.search, 10 results cost 1 credit, so fewer results cost less. On every other endpoint, limit returns a 400. To keep a model’s context small, take the rows you need from data.results, or use fields through the MCP server to keep only some keys.