Bidirectional pagination

Paginated list endpoints now support navigating backwards.

Before

Pagination was forward-only. You could move to the next page using next_cursor, but had no way to return to a previous page without starting the request sequence over from the beginning.

What changed

All paginated responses now include previous_cursor and previous_url alongside the existing next_cursor and next_url. This means you can move freely in both directions through any result set.

1{
2  "items": [...],
3  "next_cursor": "eyJpZCI6...",
4  "next_url": "https://api.wrift.ai/v1/models?cursor=eyJpZCI6...",
5  "previous_cursor": "eyJpZCI6...",
6  "previous_url": "https://api.wrift.ai/v1/models?cursor=eyJpZCI6..."
7}

This is particularly useful for building paginated UIs on top of the API — table views, dashboards, and explore pages can now support both "next" and "previous" navigation without client-side workarounds like caching earlier pages.