Mentions are the evidence layer behind Arcmira. Each row links one entity to one piece of media with timestamps, surrounding context, sentiment, and source-channel metadata.Documentation Index
Fetch the complete documentation index at: https://docs.arcmira.com/llms.txt
Use this file to discover all available pages before exploring further.
entity_*).
Only
person entities can have appearances. For organizations, products, topics, and channels, rows are always mentions. Passing is_appearance=true for a non-person entity returns 400 appearances_person_only. See Appearances vs. mentions.Minimal request
cURL
Node 20+
entity_id or entity_name is required.
By name
entity_type is optional but strongly recommended when names are ambiguous.
Filters
| Parameter | Description |
|---|---|
entity_id | Canonical ent_<id>. Mutually exclusive with entity_name. |
entity_name | Human-readable name. Pair with entity_type to disambiguate. |
entity_type | One of person, organization, product, topic, channel. |
channel_id | Restrict to a single channel (YouTube channel ID). |
channel_name | Substring match on the source channel name. |
q | Free-text search over mention description, media title, entity name, channel name. |
sentiment | One of positive, neutral, negative (uses the same thresholds as the web app). |
is_appearance | true or false. Person entities only. |
date_from | ISO date. Lower bound (inclusive) on published_at. |
date_to | ISO date. Upper bound (inclusive) on published_at. |
details | "full". Attaches matching commercial recommendations to each row. Pro+ + recommendations:read. |
limit | 1–100. Default 20. |
cursor | Opaque cursor from a previous response’s next_cursor. |
Response shape
is_appearanceis alwaysfalsefor non-person entities, regardless of the underlying row.sentimentis the bucketed label;sentiment_scoreis the raw[-1, 1]score.start_timestamp/end_timestampare seconds into the source media when available.source_channelis null for non-YouTube media.
Pagination
Mentions paginate via cursors. Pass the previous response’snext_cursor as the cursor query parameter. has_more tells you whether to keep going. See Pagination for the full pattern.
Enrichment with details=full
Pro+ callers with recommendations:read can attach matching commercial recommendations to every mention row by adding details=full. The rest of the response shape is unchanged.
recommendations block listing any commercial-pipeline rows that share the same (entity, media) pair:
recommendations.itemsis[]for rows with no matching commercial extraction. The block is always present whendetails=full.- Items reuse the public
com_*ID scheme — use them withPOST /v1/feedbackto correct individual rows. - Disputed recommendations are excluded; there is no
include_disputedknob on the mentions endpoint. - Without
details=full, the response is identical to v1.0.0 — no new fields, no breaking changes.
403 recommendations_not_enabled when details=full is requested. Pro+ keys missing recommendations:read receive 403 insufficient_scope. See Commercial intelligence for the gate details.
details=full charges one row per mention plus the premium row rate for each commercial enrichment item. See Usage & billing.
Entity-scoped variant
If you already have anent_<id>, the entity-scoped path is identical except for how you express the target: