> ## 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. # Get started with Teams > Create an Arcmira team, upgrade from an individual plan, invite members, and set up domain-based joining. Arcmira works for individuals and teams. The Teams plan adds centralized billing, member management with roles and seat types, usage analytics, admin spend controls, SAML and OIDC SSO, and a read-only [Teams Admin API](/docs/teams/analytics#teams-admin-api). Need SCIM provisioning, pooled usage, or invoice billing? See [Enterprise](/docs/teams/enterprise). ## Create a team * **New teams**: go to [arcmira.com/team/new-team](https://arcmira.com/team/new-team). * **Existing individual users**: open [Dashboard → Members](https://arcmira.com/dashboard?tab=members) and click **Upgrade to Teams**. Pick a team name, the number of members you are starting with (minimum 2), and monthly or yearly billing. Every member starts on a Standard seat; upgrade individual members to Premium (5x usage) later from the Members tab. See [Pricing](/docs/teams/pricing) for seat prices. Checkout runs through Stripe. The team is created once payment completes, and you land back in the dashboard as its Admin. Invite by email or share an invite link from the Members tab. Seats are billed per active member and prorated, so mid-cycle additions charge only for the remaining days. See [Members, roles, and seat types](/docs/teams/members) for all four join paths. You can also enable domain matching so teammates with a verified, matching email domain join without an invite. Verify your domain and enable it in **Dashboard → Settings → Domains**. SAML 2.0 and OIDC SSO are included on Teams at no extra cost. Configure a provider in **Dashboard → Settings → Single Sign-On**; new users are enrolled automatically on first sign-in. See [SSO](/docs/teams/sso). ## Joining a team as an existing subscriber Joining a team gives you the team's access tier and included rows through your seat. Joining a team does not cancel a personal subscription. If you hold an individual plan and join a team, your personal subscription keeps billing until you cancel it yourself from [Dashboard → Billing](https://arcmira.com/dashboard?tab=billing). ## FAQ ### How can I set up a team without using Arcmira myself? Set yourself as an [Unpaid Admin](/docs/teams/members#roles). Unpaid Admin seats are free, carry full administrative capabilities, and have no product access. Teams need at least one paid member, so create the team, invite a paid member, then change your own role. ### How does billing work when members come and go? Billing is per active seat and centralized on the team. New members are charged prorated for the remainder of the billing period. Removing a member who has consumed included rows this cycle keeps the seat billed until the cycle ends; otherwise the seat is released immediately with a prorated credit. Details on [Pricing](/docs/teams/pricing). ### Can teammates join without an invite? Yes, two ways: domain matching (verified email domain, self-serve join from the dashboard) and SSO auto-enrollment on first sign-in. Both require a verified domain. See [Members](/docs/teams/members#add-a-member) and [SSO](/docs/teams/sso). ### How do I see what my team is using? Team analytics live on the dashboard Overview tab: rows consumed per day, active members, API requests, and a per-member breakdown with CSV export. See [Analytics](/docs/teams/analytics).