fix: update paginated endpoints (#12)

Author: stainless-app[bot]

README.md

@@ -81,6 +81,75 @@ Nested request parameters are [TypedDicts](https://docs.python.org/3/library/typ
 
 Typed requests and responses provide autocomplete and documentation within your editor. If you would like to see type errors in VS Code to help catch bugs earlier, set `python.analysis.typeCheckingMode` to `basic`.
 
+## Pagination
+
+List methods in the Codex API are paginated.
+
+This library provides auto-paginating iterators with each list response, so you do not have to request successive pages manually:
+
+```python
+from codex import Codex
+
+client = Codex()
+
+all_entries = []
+# Automatically fetches more pages as needed.
+for entry in client.projects.entries.list(
+    project_id=0,
+):
+    # Do something with entry here
+    all_entries.append(entry)
+print(all_entries)
+```
+
+Or, asynchronously:
+
+```python
+import asyncio
+from codex import AsyncCodex
+
+client = AsyncCodex()
+
+
+async def main() -> None:
+    all_entries = []
+    # Iterate through items across all pages, issuing requests as needed.
+    async for entry in client.projects.entries.list(
+        project_id=0,
+    ):
+        all_entries.append(entry)
+    print(all_entries)
+
+
+asyncio.run(main())
+```
+
+Alternatively, you can use the `.has_next_page()`, `.next_page_info()`, or `.get_next_page()` methods for more granular control working with pages:
+
+```python
+first_page = await client.projects.entries.list(
+    project_id=0,
+)
+if first_page.has_next_page():
+    print(f"will fetch next page using these details: {first_page.next_page_info()}")
+    next_page = await first_page.get_next_page()
+    print(f"number of items we just fetched: {len(next_page.entries)}")
+
+# Remove `await` for non-async usage.
+```
+
+Or just work directly with the returned data:
+
+```python
+first_page = await client.projects.entries.list(
+    project_id=0,
+)
+for entry in first_page.entries:
+    print(entry.id)
+
+# Remove `await` for non-async usage.
+```
+
 ## Handling errors
 
 When the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of `codex.APIConnectionError` is raised.