Agent-Ready Video

Draft 1.0, proposed

Changelog

Changes to the spec, the examples, this site and the standards process, newest first. The same entries appear in spec section 6.

  1. Unreleased

    Reporting use, usage_url and receipt typ #

    • Asset language is now defined as the main spoken language, a BCP 47 tag, and the same value as schema.org inLanguage. Added optional caption_languages for subtitle and caption tracks, the same list as schema.org subtitleLanguage. An agent that answers in another language SHOULD say which language the video is spoken in and whether captions in the user's language exist (sections 3.1 and 4.1). Both fields are optional, so existing 1.0 documents stay valid.
    • Added change signals. Asset modified_at (section 3.1). Catalog changes read with since, until, after, next_after, next_since and removed, its error codes, 410 for a dropped cursor and 404 for a catalog that goes away (section 3.7.1). HTTP validators (section 3.7.2). Sitemap lastmod and IndexNow removal rules (section 4.1). L1 change-signal checks (section 5). New example catalog-changes.json. All fields are optional, so existing 1.0 documents stay valid.
    • Added optional idempotency_key to usage-request.schema.json (section 3.5.1). A repeat of a recorded report by the same caller, for the same moment, action and key, within the origin's dedupe window, returns the original receipt and records no second use.
    • Added section 3.5.1 Reporting use and usage-request.schema.json: one request for record_usage and the new optional Manifest usage_url (https, requires jwks_url). Errors are {"error": code} with moment_invalid (400), asset_not_found (404), action_not_permitted and quote_over_limit (403). A receipt's served_to.agent is always the verified caller or unverified, never a caller claim.
    • A UsageReceipt JWS header MUST carry typ: "arv-receipt+jwt" and a kid in jwks_url, and verifiers reject any other typ. Conformance check 17 adds negative tests.
    • Public source repository created with the spec text, schemas, examples, conformance checklist and CI checks.

  2. arv URI scheme registered at IANA #

  3. 2026-09-25 #

  4. Entitlement and payment fields, site launch, registrations #

    • W3C Community Group proposal under staff review; AgentCDN will contribute the draft under the W3C CLA at launch; draft charter added.
    • First origin live: AgentCDN serves an ARV 1.0 manifest at https://agentcdn.com/.well-known/arv, an ARV catalog, RSL 1.0 license terms, the Content-Usage header, range-addressed moment ids and an MCP origin profile (server agentcdn-arv). Self-declared, not yet validated; the validator is not released.
    • Added optional entitlement and payment objects to RightsSummary and PlaybackDescriptor, optional payment_ref and entitlement_ref to UsageReceipt, and optional entitlement_url and payment_terms_url to Manifest. Defined in 1.0, optional to implement. An L3 origin that sets required: true returns 402 or 403 with the challenge URL.
    • Added the example rights-summary-account-link.json for a restricted moment that needs account linking.
    • Launched the website at https://agentreadyvideo.org.
    • Submitted a provisional URI scheme request for arv: to IANA.
    • Proposed a W3C Community Group for Agent-Ready Video.
    • Opened a schema.org issue for the Clip @id convention: https://github.com/schemaorg/schemaorg/issues/4923

  5. Draft 1.0 proposed #

    • Draft 1.0 proposed: Asset, Moment, RightsSummary, PlaybackDescriptor, UsageReceipt, Manifest and Catalog, with JSON Schemas at https://agentreadyvideo.org/schema/1.0/.
    • Name: Agent-Ready Video (ARV). URI scheme arv:. Version field "arv": "1.0".
    • A moment is an address: an agent may name any range, the origin may snap or cap it and returns the range it applied.
    • Playback is start only, with optional cue points. end_ms on a descriptor is advisory, and players do not stop at it.
    • Three conformance levels (L1, L2, L3) with 18 checks.

These entries come from CHANGELOG.md in the source repository. Follow changes as they happen on GitHub.