> ## 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. > ## 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://docs.arcmira.com/llms.txt, then fetch the matching page's .md export. Each capability has a self-contained ' 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. # Read back a feedback submission and its review status > Returns the submission (id, type, query, notes, created_at) plus its per-correction rows, each with a review status in the public vocabulary: pending_review, needs_information, accepted, accepted_with_changes, rejected, withdrawn, applied, reverted (accepted means a reviewer agreed; applied means the change is live in the index). Only the submitting user's keys can read a submission; unknown ids and other users' submissions both return 404 (never 403). ## OpenAPI ````yaml /openapi/arcmira-v1.json get /v1/feedback/{feedback_id} openapi: 3.1.0 info: title: Arcmira API version: 1.0.0 contact: name: Arcmira url: https://arcmira.com servers: - url: https://api.arcmira.com security: [] paths: /v1/feedback/{feedback_id}: get: tags: - Feedback summary: Read back a feedback submission and its review status description: >- Returns the submission (id, type, query, notes, created_at) plus its per-correction rows, each with a review status in the public vocabulary: pending_review, needs_information, accepted, accepted_with_changes, rejected, withdrawn, applied, reverted (accepted means a reviewer agreed; applied means the change is live in the index). Only the submitting user's keys can read a submission; unknown ids and other users' submissions both return 404 (never 403). operationId: get_feedback responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/FeedbackReadbackResponse' '400': description: Invalid request content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '401': description: Authentication error content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '402': description: Quota exceeded content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '403': description: Permission error content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '404': description: Not found content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '409': description: Conflict content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error '500': description: Server error content: application/json: schema: type: object properties: error: type: object properties: type: type: string code: type: string message: type: string param: type: string doc_url: type: string request_id: type: string required: - type - code - message - doc_url - request_id required: - error security: - bearerAuth: [] - apiKeyAuth: [] components: schemas: FeedbackReadbackResponse: type: object properties: feedback_id: type: integer description: Id of the feedback record. type: type: string description: >- The feedback type as submitted. Values: recommendations, channel_sponsors, mentions, entities_search, entities, channels, monitor_alert, appearances, search. status: type: string enum: - pending_review - needs_information - accepted - accepted_with_changes - rejected - withdrawn - applied - reverted description: >- Submission-level rollup of the per-correction statuses. Review status in the public vocabulary. Values: pending_review (submitted; a reviewer has not finished with it), needs_information (a reviewer needs more detail from you; add context in a support thread quoting the feedback_id), accepted (the correction was accepted as submitted), accepted_with_changes (accepted, but the reviewer resolved it differently than proposed), rejected (reviewed and declined), withdrawn (withdrawn by the submitter before review), applied (the accepted change is live in the index; accepted does not imply applied), reverted (a previously applied change was rolled back). query: type: object additionalProperties: {} description: The query object the feedback was attached to, as submitted. notes: type: - string - 'null' description: The top-level notes as submitted. Null when none were supplied. created_at: type: - string - 'null' description: When the submission was created. corrections: type: array items: $ref: '#/components/schemas/FeedbackReadbackCorrection' description: >- Per-correction rows with their individual review statuses, in submission order. required: - feedback_id - type - status - query - notes - created_at - corrections FeedbackReadbackCorrection: type: object properties: item_id: type: string description: >- The correction target id as submitted (or a generated placeholder when omitted). item_kind: type: string description: >- Inferred kind of the target. Values include: recommendation, sponsor_entity, entity, entity_merge, mention, appearance, alert, alert_expectation, unknown. issue_type: type: - string - 'null' description: >- The issue_type as submitted. Null when the correction carried only a reason or mention_class. reason: type: - string - 'null' description: >- The commercial reason code as submitted. Null unless the correction was a commercial-class dispute. suggested_change: type: - object - 'null' additionalProperties: {} description: >- The suggested_change object as submitted. Null when none was supplied. notes: type: - string - 'null' description: The per-correction notes as submitted. Null when none were supplied. status: type: string enum: - pending_review - needs_information - accepted - accepted_with_changes - rejected - withdrawn - applied - reverted description: >- Review status in the public vocabulary. Values: pending_review (submitted; a reviewer has not finished with it), needs_information (a reviewer needs more detail from you; add context in a support thread quoting the feedback_id), accepted (the correction was accepted as submitted), accepted_with_changes (accepted, but the reviewer resolved it differently than proposed), rejected (reviewed and declined), withdrawn (withdrawn by the submitter before review), applied (the accepted change is live in the index; accepted does not imply applied), reverted (a previously applied change was rolled back). resolution_note: type: - string - 'null' description: >- Reviewer-written public note about how the correction was resolved. Null until a reviewer leaves one. created_at: type: - string - 'null' description: When the correction row was created. required: - item_id - item_kind - issue_type - reason - suggested_change - notes - status - resolution_note - created_at securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: arc_sk_* apiKeyAuth: type: apiKey in: header name: x-api-key ````