1. Executive Summary

The Agentic Readiness Index (ARI) is a benchmarking framework for evaluating the degree to which media and entertainment technology platforms are operable by autonomous software systems.

ARI does not measure whether a company has AI features.

ARI measures whether autonomous coding agents and operational agents can discover, authenticate, configure, orchestrate, monitor, govern, and economically interact with a platform through machine-operable interfaces under realistic enterprise governance constraints.

ARI is therefore an operational infrastructure benchmark, not an AI feature benchmark.

The primary audience includes:

• media technology buyers
• vendors
• product leaders
• infrastructure teams
• ecosystem partners
• analysts
• investors
• agentic workflow builders

2. Core Thesis

The next generation of enterprise software competition may increasingly depend on which platforms are most operable by autonomous systems.

Traditional enterprise software was designed around:

• human operators
• graphical user interfaces
• manual configuration
• implementation specialists
• professional services teams
• seat-based usage patterns

ARI assumes that future-ready infrastructure increasingly supports:

• machine-operable workflows
• autonomous provisioning
• programmatic governance
• software-to-software execution
• agent-mediated orchestration
• governed machine access
• usage-based or transactional economic models

The framework measures:

autonomous operability under realistic enterprise governance conditions.

3. What ARI Measures

ARI measures:

• agent-accessible documentation
• machine execution surfaces
• CLI/MCP/equivalent agent surfaces
• execution surface completeness
• autonomous provisioning capability
• governed operational accessibility
• workflow composability
• operational observability
• machine-operable governance
• commercial alignment with autonomous consumption

ARI does not measure:

• overall product quality
• customer satisfaction
• market share
• feature breadth
• generic AI sophistication
• AI marketing
• embedded copilots
• chatbot functionality

A company may have sophisticated AI features and still score poorly if its platform is not operable by autonomous systems.

A company may have little AI branding and score highly if it exposes strong machine-operable infrastructure.

4. Foundational Assessment Question

Every ARI assessment is governed by one question:

Could a modern autonomous coding agent independently implement and operate this platform using available machine interfaces and operational documentation with minimal human UI dependency?

This question governs scoring, evidence collection, and recommendations.

5. Public Discoverability vs Governed Operability

ARI does not assume that all operational interfaces should be fully public.

Enterprise systems, especially in media and entertainment, may have valid reasons to restrict access:

• rights complexity
• security concerns
• premium content protection
• financial workflows
• compliance requirements
• partner ecosystem boundaries

ARI distinguishes between:

A platform may score highly without unrestricted public exposure if it supports governed autonomous operation.

However, systems that depend on undocumented workflows, human-only onboarding, UI-only administration, or professional-services mediation should score lower.

6. Evidence Accessibility Tiers

ARI recognizes four evidence/access tiers.

Governed access is not inherently penalized.

Opaque access is penalized when it prevents reproducible assessment or autonomous operation.

7. Multi-Model Assessment Model

ARI assessments should be performed by multiple independent LLM evaluators.

Recommended evaluators:

• ChatGPT
• Gemini
• Claude

Each evaluator receives:

• the same rubric
• the same evidence set
• the same scoring instructions
• the same assessment template

Each evaluator returns:

• category scores
• subcategory scores
• penalties
• evidence notes
• confidence level
• recommendations
• final score

Final ARI score:

A product is assessed by all three evaluators in parallel. At least two of the three must return a valid result for the product to be scored (a single result is treated as insufficient evidence). The final score averages only the evaluators that ran:

ARI Final Score = (sum of participating evaluator scores) / (evaluators that ran)

Each individual signal and penalty is averaged the same way: its credit is the fraction of participating evaluators that detected it, applied to that item's weight. So when two of three evaluators run, an item detected by only one of them contributes half of its weight. This consensus averaging is why the index rewards capabilities the models agree on and damps single-model noise.

Human role:

• define rubric
• define weights
• review anomalies
• improve methodology
• manage evidence quality

Humans are prevented from overriding scores directly.

8. Scores and Classifications

ARI should publish both numeric scores and classifications.

Numeric scores preserve precision and enable trend tracking.

Classifications improve legibility and sharing. The score-range → classification band table is published on the methodology page, driven by the active rubric.

9. ARI Scoring Framework

Total score: 100

Category 1 — Agent-Accessible Documentation

Objective: Can an autonomous agent learn how to operate the platform from available documentation?

Penalties:

Category 2 — Machine Execution Surfaces

Objective: Can autonomous systems execute operational tasks programmatically?

Penalties:

Category 3 — Execution Surface Completeness

Objective: How completely do CLI/MCP/API/agent surfaces cover the operational lifecycle?

This category addresses sincerity of implementation. A vendor should not receive high agentic-readiness credit for exposing a superficial CLI, toy MCP server, read-only adapter, or narrow wrapper that covers only a small portion of platform functionality.

Lifecycle areas:

Scoring:

Rules:

• Do not count endpoints mechanically.
• Assess lifecycle coverage, not command count.
• Read-only coverage is materially weaker than execution authority.
• Admin/governance coverage matters.
• Recovery and observability coverage matter.
• Thin wrappers should receive low scores.

Penalties:

Category 4 — Autonomous Provisioning and Configuration

Objective: Can autonomous systems provision, configure, and administer the platform without significant human mediation?

Penalties:

Category 5 — Commercial Agentic Alignment

Objective: Can autonomous systems economically transact with the platform?

Penalties:

Category 6 — Governance and Operational Trust

Objective: Can enterprises safely delegate operational authority to autonomous systems?