API pagination

Every collection endpoint uses cursor pagination, not offsets.

Parameters

• limit — page size, 1 to 100 on most collections (the server caps oversized values)
• cursor — the opaque pagination.next_cursor value from the previous page

Walking a collection

1. Request the first page with just limit.
2. Read pagination.next_cursor from the response.
3. Request the next page with that cursor.
4. Stop when next_cursor is null.

Why cursors

Results are ordered by creation time descending. With offsets, rows inserted while you page cause records to be skipped or repeated. A cursor points at a fixed position, so paging stays stable during writes.

Important notes

Cursors are opaque. Do not parse, build or store them long term — treat them as a token that is valid for the next request in the same sequence.