List mentions

Everything your keywords caught, newest first, across every Source and every keyword on the Account, annotated with the sentiment, intent and agent readings you have switched on, and filterable on both. Cursor-paged: pass the response nextCursor back unchanged. Its absence means the last page. To count mentions (per day, per Source, per sentiment, per author or term) call GET /v1/mentions/stats instead of paging: one free call, and the same numbers Insights shows. Free in the default text mode. Set mode=semantic to search by meaning instead of by substring. That path asks the embedding index and charges — at the same rate, through the same ten-minute cache, as the dashboard. Leave it out and the read is free. keyword takes a keyword id from GET /v1/keywords and reads that keyword’s mentions only, including what its searches caught before they last changed. run takes the run.id POST /v1/explore answered and reads that kept run’s mentions only, free: the way to come back to a run without paying for it again. source, sentiment and intent are repeatable filters — ?sentiment=negative&sentiment=question returns both, and repeated values of one key are OR’d while different keys are AND’d. unread selects mentions nothing has classified yet. Filtering on sentiment or intent reads the polled stream only: kept Explore-run items carry no reading. author is repeatable too, and exact — the handle as the Source writes it, with no leading @ and no u/. Use q to search text. A handle you have never seen returns an empty page rather than an error, and a mention with no author never matches: not every Source carries a byline, and none carried one before author extraction shipped for it. engagement_min keeps mentions with at least that many interactions — likes, replies, reposts, comments or score, per Source. It never counts views. Mentions with no counters at all are left out rather than read as zero: RSS items and AI answers report no audience, and mentions recorded before 2026-09-04 predate the field. Counters are captured when we collect an item and never refreshed, so the threshold reads against recent mentions. Like sentiment and intent, it reads the polled stream only. engagement is a per-Source rule: <source|*>:<metric><operator><number>, repeatable — ?engagement=x:likes>=100&engagement=reddit:score>50. Metrics are likes, replies, reposts, comments, score, views, plus total for the interaction sum engagement_min reads (engagement_min=10 is exactly engagement=*:total>=10). Operators are >=, >, =, <, <=; the number is a whole number and may be negative, since Reddit and Lemmy net downvotes out. A Source no rule names passes — ?engagement=x:likes>=100 narrows X and leaves Hacker News alone — a named rule overrides * for its own Source, and several rules on one Source are ANDed; use source= to ask for one Source. A metric that was never counted satisfies nothing, < included: RSS items and AI answers report no audience, YouTube reports no likes, and mentions recorded before 2026-09-04 predate the field, so engagement=youtube:likes<10 returns none of them rather than all of them. Send engagement or engagement_min, never both. Bound the window at both ends with since and until — ?since=2026-08-03T00:00:00Z&until=2026-08-05T23:59:59Z is those three days and nothing else. until is inclusive; absent, the window stays open at the top.