---
id: "prereq-api-pagination"
type: "prereq"
source_timestamps: ["00:01:11", "00:08:21"]
tags: ["web-architecture", "apis"]
related: ["concept-human-affordance-bottleneck"]
sources: ["s20-50x-faster"]
sourceVaultSlug: "s20-50x-faster"
originDay: 20
---
# Understanding API Pagination

## What You Need to Know

The speaker frequently references **pagination** as a core flaw in current tools. To follow the argument, you must understand:

- Traditional APIs return data in **small chunks** (typically 50 or 100 records per page)
- This was designed to prevent overwhelming **human interfaces** and **human memory**
- Each page requires a separate HTTP round-trip with authentication, parsing, and continuation tokens

## Why It Matters Here

Recognizing pagination as a **human affordance** is key to understanding why agents — which can process millions of rows instantly — are slowed down by legacy APIs. This is the canonical concrete instance of [[concept-human-affordance-bottleneck]].

## Connection to the Larger Argument

- Pagination is what makes [[concept-mcp-illusion]] a real problem (wrapping a paginated API in MCP keeps the pagination)
- Eliminating it is one motivation for [[concept-agentic-primitives]]
- It's why Layer 2 of [[framework-web-rebuild-layers]] is necessary

## Related

- [[concept-human-affordance-bottleneck]]
- [[concept-mcp-illusion]]
- [[concept-agentic-primitives]]