Live feeds page with limit and offset on get_top_trends. limit is how many rows to return. offset is how many leading rows to skip. Defaults: limit 25, offset 0. Max limit is 200. The HTTP call is POST https://api.trendsapi.ai/api. Parse the string body. The mode itself is on get_top_trends.
limit is page size
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"Google Trends","limit":3,"offset":2}
A pull on 27 Aug 2026 with that body returned as_of_ts 2026-08-27T18:01:38.235804+00:00, count 3, and data ranks 3, 4, 5 (nepal, carl dean, jed york). The first two board rows were skipped. Rank 1 is not on this page.
limit 10 with offset 0 is the first ten leaders. limit 10 with offset 10 is the next ten.
offset skips ranks
data[0][0] is the board rank, not offset + 1 rewritten to 1. Do not relabel rank 3 as "page item 1" in a warehouse that already stores rank. Join pages on as_of_ts plus rank.
offset past the end of the board returns an empty data array and a count of 0. That is not a 404.
What count means
count is len(data) for this response. It is not a total. There is no total field on the MCP payload in this session. Stop paging when count is 0 or less than limit.
sort rank_change uses the same two fields. Climber order is on rank_change sort. Four types still need category on every page. Caps stay on pricing.