Count mentions

List mentions (brand mentions your listeners matched), cursor-paginated. `sort` is `newest` (default, by `datePublished` descending) or `fitScore` (by AI fit score descending, unscored mentions last). **Cursor pagination only** — mentions insert continuously, so this endpoint does not support offset/page pagination. Pass `meta.nextCursor` from a response as `cursor` on the next request. When `meta.hasMore` is `false`, there is nothing more to fetch. A cursor is only valid for the `sort` it was minted under; reusing it with a different value returns a validation error. Because `newest` sorts by publish date, a mention backfilled or found via a delayed crawl can carry an older `datePublished` than mentions you've already paginated past, and will not appear in a subsequent page. `sort=fitScore` has a similar but more general risk: AI fit score can be overwritten by reanalysis after insert, so a mention re-scored while you're mid-pagination can occasionally be skipped or duplicated across pages. Prefer `sort=newest` if you need a gap-free stream. `status` defaults to `ready` (unarchived). Note that `status` and AI analysis (`ai.*`, including `fitScore`) are point-in-time, not live: a mention synced before it was archived or re-scored will not reflect the change unless you re-fetch it. `platform`, `sentiment`, `fitScore`, `languages`, `includeIntents`/`excludeIntents`, `listenerIds`/`excludeListenerIds`, and `includeKeywords`/`excludeKeywords` all take comma-separated values. `dateFrom`/`dateTo` filter on `datePublished` (note: independent of `sort`). **Read-only** — this endpoint does not consume credits.