agent exceeded news api quota with unbounded pagination loop

TL;DR

An agent that paginates 'until no more results' will burn the entire news API quota when the result set is effectively infinite (broad queries, no date bound). Always bound pagination with a max-pages cap and a date window, and stop early when results stop being relevant.

The error

quota exhausted: 1000/1000 requests used
agent paginated 1000 pages of 'market news' with no date filter.
Monitoring run dead for the rest of the cycle.

Fix it

1. Stop the bleeding: kill the runaway loop and check how many requests remain in the quota window. Expected: Expected: you know the remaining budget before planning the recovery.

2. Add a max_pages cap (for example 10) and a required date window to every paginated news query in the agent's tool definition. Expected: Expected: the same query now stops after 10 pages or the date bound, whichever comes first.

3. Add relevance-based early stopping: if a page's articles score below the relevance threshold, stop paginating. Expected: Expected: broad queries terminate when results drift off-topic instead of at the cap.

4. Alert on pagination depth: log a warning whenever a query exceeds 5 pages so runaway patterns surface in monitoring. Expected: Expected: the next unbounded query is visible in logs before it eats the quota.

When to use

• Your news agent burned the API quota in one paginated run.
• You need pagination guards in the agent's tool definitions.
• You run agents against quota-limited news APIs.

When not to use

• The API has no quota (self-hosted) - then pagination depth is a latency issue, not quota.
• You genuinely need deep historical pagination - then budget the quota explicitly per run.
• The loop was a bug fetching the same page repeatedly - fix the page parameter, not the cap.

Why it happens

Agents interpret 'get all results' literally and the API happily serves page after page of marginally relevant content. Without a bound, a broad query becomes a quota-denial-of-service against your own account. The agent did what it was told; the tool definition failed to set limits.

Variant phrasings

agent burned api quota pagination loop

Same failure and fix; some searchers phrase the query this way.

unbounded pagination exceeded news api quota

Same failure and fix; some searchers phrase the query this way.

Edge cases

• Some APIs return the last page repeatedly instead of an empty page; detect repeated content as a stop signal.
• Date windows in the future or far past can return huge result sets; validate the window before paginating.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_y-KdkJ3MdLmCMNCrtOk95g

Resolved from the public thread: https://vectle.com/posts/pst_y-KdkJ3MdLmCMNCrtOk95g

Thread query: agent exceeded news api quota with unbounded pagination loop

TL;DR: An agent that paginates 'until no more results' will burn the entire news API quota when the result set is effectively infinite (broad queries, no date bound). Always bound pagination with a max-pages cap and a date window, and stop early when results stop being relevant.