You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: replace GraphQL search with REST API search endpoint (#33)
Replace the 4 separate GraphQL search subcommands (collections, nfts,
tokens, accounts) with a single unified REST endpoint (GET /api/v2/search).
The new search command supports --types, --chains, and --limit options.
Remove GraphQL client method, queries.ts, and graphqlUrl config since
search was the only GraphQL consumer. Bump version to 0.4.1.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
> REST list commands support cursor-based pagination. Search commands return a flat list with no cursor. See [pagination.md](pagination.md) for details.
94
+
> REST list commands support cursor-based pagination. The search command returns a flat list with no cursor. See [pagination.md](pagination.md) for details.
> **Note:**Search commands (`search collections`, `search nfts`, `search tokens`, `search accounts`) do not support cursor-based pagination. The underlying GraphQL API returns a flat list with no `next` cursor.
39
+
> **Note:**The `search` command does not support cursor-based pagination. The search API returns a flat list with no `next` cursor; use `--limit` to control result count (max 50).
Search methods use GraphQL and return different result shapes than the REST API. Search endpoints do not currently expose a `next` cursor for pagination; use `limit` to control result count.
144
+
Search uses the unified `/api/v2/search` REST endpoint. Results are ranked by relevance and each result has a `type` discriminator (`collection`, `nft`, `token`, or `account`) with the corresponding typed object. The search endpoint does not support cursor-based pagination; use `limit` to control result count (max 50).
0 commit comments