> ## Documentation Index
> Fetch the complete documentation index at: https://arcmira.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Arcmira has three API capabilities: Search (entities, mentions, appearances, commercial intelligence), Monitors (trackers plus alert delivery), and Transcripts (read, generate, correct). Community Review is the cross-surface correction layer.
> Discover pages at https://arcmira.com/docs/llms.txt, then fetch the matching page's .md export. Each capability has a self-contained '<capability> for coding agents' page; prefer it.
> Auth: Authorization: Bearer arc_sk_... or x-api-key: arc_sk_... (x-api-key wins if both are sent). Never put keys in browser code. Check GET /v1/me for tier, scopes, and remaining rows before metered pulls.
> Search: resolve names with GET /v1/entities/lookup and pin ent_* IDs before pulling metered rows. Only person entities have appearances. Mention and recommendation rows carry canonical numeric timestamps in start_seconds/end_seconds (integer seconds; 0 means full episode); the MM:SS string fields are deprecated. Commercial routes need Pro+ tier AND the recommendations:read scope and bill 10 rows per row.
> Monitors: a tracker watches one entity; a monitor groups trackers with shared delivery (email, Slack, HMAC-signed webhooks). Create trackers with POST /v1/trackers, then attach by id: POST /v1/monitors/{id}/trackers { trackerIds: [...] }. Each fired alert occurrence debits 100 rows. Poll GET /v1/monitors/{id}/alerts?n= for recent deliveries. Send Idempotency-Key on every POST/PATCH.
> Transcripts: switch on the access field (unlocked, locked, premium_pending, not_transcribed, unauthenticated). Honor Retry-After when polling POST /v1/transcriptions jobs. Corrections (POST /v1/videos/{video_id}/corrections; kinds line_edit, speaker_reassign, speaker_identify, add_person, entity_tag, segment_rewrite) cost 0 rows; anchored kinds need revision + anchor.contentHash (djb2 base-36); handle 409 (re-anchor) and 412 (expectedSeq). segment_rewrite replaces an inclusive segment range with new segments (empty replacements array deletes; timestamps repaired server-side).
> Community Review is free (0 rows) and surface-typed: POST /v1/feedback with a type matching the surface you called, the reproducing query, and corrections targeting public IDs (ent_*, men_*, com_*). Nothing auto-applies. Do not send untyped notes.
> Errors: switch on error.code, follow doc_url, quote X-Request-Id to support. Honor Retry-After on 429. Retries of POST/PATCH must reuse the same Idempotency-Key; replays return Idempotency-Replayed: true.
> Teams Admin API: GET /v1/team/members, /v1/team/spend, /v1/team/usage-events (cursor-paginated, 90-day bound) are read-only and require a team-scoped API key created by a team admin; personal keys get 403 team_key_required.

# Changelog

> Product updates and release notes for the Arcmira API.

<Update label="July 2026" description={<div className="changelog-month-index"><div><a href="#community-review-across-every-surface">Community Review across every surface</a></div><div><a href="#transcripts-and-transcriptions-v1-2-0">Transcripts and Transcriptions</a></div></div>} rss={{ title: "July 2026", description: "Community Review across every surface, and Transcripts and Transcriptions v1.2.0." }}>
  ## Community Review across every surface

  Every result-bearing surface now accepts typed feedback, and submissions are readable back.

  * **New feedback types** on `POST /v1/feedback`: `monitor_alert` (dispute a fired alert by row ID), `appearances` (`person_not_present`, `wrong_person`, `wrong_appearance_role`), and `search` (single-result resolutions, with `observed_rank`).
  * **Readback**: `GET /v1/feedback/{feedback_id}` returns your submission with per-correction review status, from `pending_review` through `applied` and `reverted`.
  * **Typed `suggested_change`**: documented as a union per `issue_type` in the OpenAPI spec; existing loose submissions continue to validate.
  * **Alert public IDs**: alert history rows carry `mention_id` (`men_*`) and `entity_id` (`ent_*`), joining directly against mention rows and entity reads.

  [Read the Community Review catalog →](/docs/feedback)

  ## Transcripts and Transcriptions (v1.2.0)

  Premium transcripts arrived: diarized, speaker-identified, entity-annotated, and community-correctable.

  * **Read**: `GET /v1/transcripts/{video_id}` with permanent per-video unlocks (`?unlock=true`), priced in rows per 15-minute block.
  * **Generate**: `POST /v1/transcriptions` submits any public YouTube video; poll with `Retry-After`, `etaSeconds`, and `nextPollSeconds`.
  * **Correct**: unified `POST /v1/videos/{video_id}/corrections` covers line edits, speaker edits, speaker identifications, and entity tags, with idempotent replay, per-video sequence numbers (`412` with `expectedSeq`), and anchor validation (`409` with `currentRevision`).
  * Transcript surfaces are premium-only: videos without a premium analysis return a preliminary scan with detected entity counts instead of segments.

  [Read the Transcripts guide →](/docs/transcripts)
</Update>

<Update label="June 2026" description={<div className="changelog-month-index"><div><a href="#community-review">Community Review</a></div></div>} rss={{ title: "June 2026", description: "Community Review: structured feedback became the documented path for correcting the index." }}>
  ## Community Review

  Structured feedback became the documented path for correcting the index.

  * `POST /v1/feedback` accepts notes, corrections, merge suggestions, and classification review requests against the exact query you ran.
  * Public submissions create review items only; accepted changes are applied by reviewers, and submitter reputation accrues to the account and API key over time.
  * Commercial submissions use the same access as the data being reviewed: **Pro+** plus `recommendations:read`.

  [Read the Community Review catalog →](/docs/feedback)
</Update>

<Update label="May 2026" description={<div className="changelog-month-index"><div><a href="#commercial-intelligence-v1-1-0">Commercial intelligence</a></div><div><a href="#entity-and-mentions-surface-v1-0-1">Entity and mentions surface</a></div></div>} rss={{ title: "May 2026", description: "Commercial intelligence v1.1.0 went live for Pro+ plans, plus the entity and mentions surface v1.0.1." }}>
  ## Commercial intelligence (v1.1.0)

  The commercial evidence layer went live for Pro+ plans.

  * **Recommendations API**: `GET /v1/recommendations` and `GET /v1/entities/{id}/recommendations`, filtered by `mention_class` (`ad_read` / `endorsement` / `mention` / `all`), `channel_id`, `min_confidence`, dates, and `include_disputed`. Public IDs use the `com_*` scheme.
  * **Channel sponsors**: `GET /v1/channels/{channel_id}/sponsors` with `min_ad_reads` (default 3) and `status` filters, built on the recurring-sponsor rules behind Arcmira's internal advertiser dashboards.
  * **Entity discovery**: `GET /v1/entities/search`, fuzzy, ranked, free, with `has_recommendations_data`.
  * **Mention enrichment**: `GET /v1/mentions?details=full` attaches matching commercial rows (verbatim quotes, promo codes, offers, confidence).
  * **Summaries and teasers**: `recommendations_summary` on entity reads; `sponsor_count` visible to every caller on channel reads.
  * **Gating**: new `recommendations:read` scope, `recommendations_api_enabled` on `/v1/me`, and error codes `recommendations_not_enabled`, `invalid_feedback_request`, `channel_not_found`, `recommendation_not_found`. Commercial rows bill at a premium per-row rate.

  [Read the Commercial intelligence guide →](/docs/commercial-intelligence)

  ## Entity and mentions surface (v1.0.1)

  * `GET /v1/entities/lookup` resolves a name (and optional `type`) to a canonical `ent_<id>`, following merge chains; `merged_from_id` marks aliases.
  * `GET /v1/entities/{id}`, `GET /v1/entities/{id}/mentions`, and `GET /v1/mentions` with entity, channel, sentiment, appearance, date, and free-text filters.
  * Non-person appearance routes return `400 appearances_person_only`; only `/v1/people/{slug}/appearances` is documented.
  * `X-Request-Id`, `X-Arcmira-Version`, and `RateLimit-*` headers stable across all v1 responses.

  [Read the Search guide →](/docs/search)
</Update>

<Update label="April 2026" description={<div className="changelog-month-index"><div><a href="#initial-public-api-surface-v1-0-0">Initial public API surface</a></div></div>} rss={{ title: "April 2026", description: "Initial public API surface v1.0.0: search, entity reads, monitors, trackers, and scoped API keys." }}>
  ## Initial public API surface (v1.0.0)

  The first public release of the Arcmira API.

  * Search and entity reads; person appearances and per-entity related lists.
  * Monitors and trackers CRUD with idempotency, plus `/alerts` recent delivery history.
  * Cursor pagination (`data` / `has_more` / `next_cursor`), a stable error envelope, and `X-Request-Id` correlation.
  * Scoped API keys: `read`, `monitors:write`, `trackers:write`.

  [Read the Quickstart →](/docs/)
</Update>