> ## 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. # Team dashboard > Where team management lives in the Arcmira dashboard: Members, Settings, Spending, Billing, and team API keys. Team management lives inside the regular [Arcmira dashboard](https://arcmira.com/dashboard), not a separate admin console. This page maps each tab. ## Overview tab The Overview tab carries team analytics for everyone on a team: a rows-per-day chart, summary stats, and a per-member usage table. Admins additionally see team spend against the monthly limit. See [Analytics](/docs/teams/analytics). ## Members tab Always visible in the sidebar. What it shows depends on your account: * **No team**: an Upgrade to Teams state with the plan's feature grid and a contact-sales banner for [Enterprise](/docs/teams/enterprise) needs. * **On a team**: the member list with role and seat badges, plus pending invites. From here admins (and, for Standard-seat Member invites, everyone) open the invite modal, which handles email invites and the shareable invite link, including rotating and revoking the link. Member rows carry the actions: change role, change seat type, set a per-member spend cap, remove, and revoke sessions. See [Members, roles, and seat types](/docs/teams/members). ## Spending tab The team spend console, for teams with on-demand usage. Admins control: * The team-wide on-demand toggle * The team monthly spending limit * The default per-member monthly cap, plus per-member overrides * "Only admins can modify on-demand settings" Members see their own resolved cap and current spend. Members never opt in personally; on-demand overage bills the team at \$0.004/row. See [Pricing](/docs/teams/pricing#on-demand-usage). ## Billing tab Seat counts by type with prorated adjustments when you add seats, the switch-to-yearly banner (20% off), and the invoice portal for payment methods and billing history. ## Settings tab Personal settings first, then team sections for admins: * **Team Spending**: pointer to the Spending tab. * **Team Domains**: add a domain, run DNS TXT verification, and toggle domain matching and invite restriction. See [Domain settings](/docs/teams/members#domain-settings). * **Team Single Sign-On**: register SAML or OIDC connections and control SSO enforcement. See [SSO](/docs/teams/sso). * **Team**: rename the team, and the danger zone for deleting it. Deleting a team permanently removes its data, including team API keys, invites, and domains. ## Team API keys Admins create team-scoped API keys from the [API Keys tab](https://arcmira.com/dashboard?tab=api-keys) by selecting the team scope at creation. Team-scoped keys unlock the read-only [Teams Admin API](/docs/teams/analytics#teams-admin-api) (`/v1/team/*`) and are revoked when their creator leaves the team. ## Audit log Administrative actions (membership changes, role changes, domain and SSO changes, spend-limit changes) are recorded for every team from day one. The audit log viewer is an [Enterprise](/docs/teams/enterprise) feature; on Teams, the view endpoint returns `enterprise_required`. Upgrading later gives you history from the day your team was created, not the day you upgraded.