Skip to main content

Segment rewrites

Transcript corrections gain a structural primitive: segment_rewrite on POST /v1/videos/{video_id}/corrections replaces any run of segments with new ones. Merge mangled ASR lines, split them, or delete the range with an empty replacements array. Timestamps repair automatically; pin start/end per replacement where the exact time matters. Anchored like line edits, free like every correction, withdrawable via DELETE /v1/corrections/segment-rewrites/{id}.Read the Transcripts coding agent reference →

Numeric-seconds timestamps on evidence rows

Mention and recommendation timestamps are now numeric. All changes are additive; nothing was removed or renamed.
  • New fields: mention rows, recommendation rows, and details=full enrichment items carry start_seconds / end_seconds (integer seconds; 0 means the full episode, no specific moment; null when the source string is null). Webhook alert payloads gain appearance.timestampSeconds.
  • Sentiment consistency: recommendation rows gain sentiment_score, the same raw [-1, 1] number mention rows already expose.
  • Deprecations: the start_timestamp / end_timestamp MM:SS strings and the recommendation sentiment number are deprecated in the OpenAPI spec. They keep working until a dated removal is announced here, per the versioning and deprecation policy. Migrate reads to the seconds fields and sentiment_score.
Read the Search coding agent reference →

Webhook secret lifecycle on v1

Pure-API consumers can now verify webhook signatures end to end, with zero-downtime secret rotation.
  • One-time secret return: monitor create/PATCH responses include monitor.webhookSecret exactly once, when the response newly enables webhook signing. Reads expose webhookSecretSet and webhookSecretHint only.
  • Rotation with overlap: POST /v1/monitors/{id}/webhook-secret/rotate returns a fresh secret once with previousSecretExpiresAt. For 24 hours, deliveries carry both X-Arcmira-Signature (new) and X-Arcmira-Signature-Previous (old).
  • Explicit re-enable: rotation never re-enables an auto-disabled webhook; PATCH { "notifyWebhook": true } is the deliberate re-enable step and clears the failure counter.
Read the Monitors coding agent reference →

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 →

Monitors API rename

The API resource is now Monitors: /v1/monitors endpoints, scope monitors:write, and payload fields monitorId, monitor_id, and monitor_name. Prior resource names for this surface are retired; rows minted before the rename keep resolving.Read the Monitors guide →

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 →

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 →

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 →

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 →

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 →