Pagination

Handle paginated responses from list endpoints.

Overview

List endpoints that return multiple items may use pagination. agntdata uses cursor-based pagination for consistent, reliable paging through results.

Request Parameters

Common pagination parameters:

Parameter	Type	Description
limit	integer	Number of items per page
cursor	string	Cursor from previous response for next page

Not all endpoints support pagination. Check each endpoint’s documentation for specific pagination details.

Response Structure

Responses include the data array and billing metadata:

{
  "success": true,
  "data": [
    { "id": "1", "title": "Item 1" },
    { "id": "2", "title": "Item 2" }
  ],
  "meta": {
    "costCents": 5,
    "purchasedBalanceCents": 944,
    "subscriptionRemainingCents": 500,
    "cached": false,
    "latencyMs": 312
  }
}

Best Practices

Use Reasonable Page Sizes

Request only what you need. Larger pages mean fewer requests but longer response times.

Handle Cursors Correctly

Cursors are opaque strings — don’t parse or modify them.

Implement Rate Limiting

When fetching many pages, add delays between requests to avoid rate limits.

Cache Results

Cache fetched data when appropriate to avoid re-fetching the same data.

Credit Consumption

Each paginated request consumes credits independently. Plan your fetching strategy to optimize credit usage.

Next Steps

Request Format

Learn about request structure.

Rate Limits

Understand rate limiting.