Skip to main content

​
What Changed

Asset list responses now use the same { object, data, has_more, next_cursor } envelope as every other list endpoint, with each item tagged object: "asset". GET /v1/assets and the find_assets MCP tool accept the opaque cursor returned as next_cursor, so the whole asset library is reachable. Previously the endpoint returned a cursor there was no way to send back, which capped every caller at one page. Semantic searches return one ranked page, so next_cursor is always null when searchTerm is set.

​
Migration

Requests pinned to 2026-08-07 keep receiving { assets, nextCursor } and asset items without the object tag — no action is required until you upgrade. When you move to 2026-08-21, read assets from data, use has_more to detect another page, and pass next_cursor back as the next request’s cursor.