> ## 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 ' 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. # Support & roadmap > How to get help fast, and what is intentionally not shipped yet. ## Support Email [hi@arcmira.com](mailto:hi@arcmira.com). Include: * The `X-Request-Id` from the affected response (also in `error.request_id` on failures). * The endpoint and method. * A timestamp (with timezone). * The first 15 characters of your API key (the `arc_sk_xxxxxxxx` prefix is fine; never paste the full secret). * The behavior you expected versus what you got. That's enough to find the trace in our logs and respond quickly. **If an API result is wrong**, prefer [Community Review](/docs/feedback): it attaches your correction to the exact query you ran and returns a `feedback_id` you can reference in follow-up threads. For new API access or custom rate limits, mention "API access" in your email and we'll route accordingly. For SCIM, pooled usage, audit log access, invoice or PO billing, or anything else on the [Enterprise plan](/docs/teams/enterprise), [contact sales](https://arcmira.com/contact-sales?product=enterprise). Enterprise includes priority support and a dedicated account manager; Teams and individual plans use the email above. ## Status API uptime and incidents will be reported on a public status page when it is live. Until then, escalations go through the email above. ## Roadmap The HTTP API is the production surface. These are deliberately deferred until v1 patterns are validated in real integrations: * **TypeScript SDK**: typed client built on the OpenAPI document, published to npm. Until then, the docs use plain `fetch` / `httpx`; everything works from any HTTP client. * **MCP server**: Search, Monitors, and Transcripts as ready-made tools for coding and research agents, so an agent can resolve entities, pull evidence, and manage trackers without a custom integration. Until then, agents integrate over HTTP with the [coding agent references](/docs/search-for-coding-agents). * **Ask a channel**: conversational Q\&A grounded in the transcripts of a channel or a set of videos you select, with every answer citing the exact segments it came from. The shape is still being decided (a dashboard surface, an API primitive, tools on the MCP server, or all three); if you have a concrete use case, tell us what you'd want to ask and where you'd want to ask it. The Teams plan (member management, roles and seat types, SSO, team analytics, centralized billing, and the [Teams Admin API](/docs/teams/analytics#teams-admin-api)) shipped in July 2026; see the [Teams docs](/docs/teams/setup) and the [changelog](/docs/changelog). Pooled usage, SCIM, and the analytics API are part of the [Enterprise plan](/docs/teams/enterprise). If any of these block your integration, write to [hi@arcmira.com](mailto:hi@arcmira.com): concrete use cases move things up the queue.