> ## 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 '<capability> 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.

# Enterprise

> The Enterprise plan: everything in Teams plus SCIM, pooled usage, audit log access, the analytics API, and invoice billing.

Enterprise is for organizations that need directory-driven provisioning, pooled usage, deeper auditability, or procurement-friendly billing. It includes everything on the [Teams plan](/docs/teams/setup), plus the capabilities below. Pricing is custom.

[Contact sales](https://arcmira.com/contact-sales?product=enterprise) to talk through your requirements.

## What Enterprise adds

| Capability                                                   | Teams | Enterprise |
| ------------------------------------------------------------ | ----- | ---------- |
| Roles, seat types, invites, domain matching                  | Yes   | Yes        |
| SAML 2.0 / OIDC SSO with JIT provisioning and enforcement    | Yes   | Yes        |
| Spend controls: team limit, per-member caps, admin-only lock | Yes   | Yes        |
| Team analytics with CSV export                               | Yes   | Yes        |
| Teams Admin API (members, spend, usage events)               | Yes   | Yes        |
| SCIM / directory sync                                        | No    | Yes        |
| Pooled usage across the team                                 | No    | Yes        |
| Audit log viewer                                             | No    | Yes        |
| Group-based spend limits                                     | No    | Yes        |
| Analytics API (programmatic chart data)                      | No    | Yes        |
| Invoice / PO billing and volume discounts                    | No    | Yes        |
| Priority support and a dedicated account manager             | No    | Yes        |

### SCIM and directory sync

Provision and deprovision members from your identity provider instead of managing invites by hand. Directory groups map onto team membership, and offboarding in the IdP removes access in Arcmira.

### Pooled usage

Teams seats each carry their own included rows. On Enterprise, included usage pools across the organization, so heavy users draw from capacity that light users leave unused.

### Audit log

Every team's administrative actions (membership, roles, domains, SSO, spend limits) are recorded from the day the team is created, on every plan. Enterprise unlocks the viewer and its API, with history intact from team creation.

### Analytics API

The dashboard's aggregated chart data (rows per day, active members, spend over time) becomes available programmatically, on top of the Teams-level member, spend, and usage-event endpoints.

### Group-based spend limits

Set on-demand caps per directory group rather than per member, on top of the team-wide and per-member controls Teams already has.

### Billing and support

Invoice and purchase-order billing, volume discounts, priority support, and a dedicated account manager.

## Moving from Teams

Enterprise is an upgrade of your existing team, not a migration: members, domains, SSO connections, API keys, and recorded audit history carry over as-is. [Contact sales](https://arcmira.com/contact-sales?product=enterprise) to get started.