Skip to main content
When a server advertises pagination, list-style results (retrieve, and graph communities) MAY include an opaque nextCursor. The client fetches the next page by repeating the request with cursor set to that value.
1

First page

Call retrieve normally. The result may include a nextCursor.
2

Next page

Repeat the same request with cursor set to the previous nextCursor.
3

Last page

A missing or empty nextCursor means there are no more results.
Cursors are opaque and server-defined — a client MUST NOT parse, construct, or reorder them. Only ever send back a cursor a server gave you, with the same query parameters. This is the identical cursor model MCP and ACP use, so a client’s pagination logic is shared across all three protocols.
Pagination and k compose: k bounds a single page; the cursor walks across pages. For reproducible paging, pin an indexVersion so the corpus doesn’t shift under you mid-walk.