The INDEX Standard

INDEX Standard 1.0

Published standardEdition 1.0 · November 2026

The INDEX Standard defines a permanent identifier, a record format, assurance levels and verifiable credentials for AI audiovisual works, so that any party can establish what a work is, who declared it and what has been verified about it.

01

A ten-character INDEX ID with a built-in check character.

02

A signed, versioned record with trusted time-stamps.

03

Content fingerprints that bind the identity to the exact files.

04

Three assurance levels: BOUND, VERIFIED and CLEARED.

05

W3C verifiable credentials from the registry, registrars, law firms and festivals.

06

Certificates in English and the holder's language, verifiable by QR code.

INDEX.FILM WORK REGISTRY BOUND INDEX.FILM WORK REGISTRY VERIFIED INDEX.FILM WORK REGISTRY CLEARED

01Scope

This Standard specifies the identifier, record, assurance levels, documents and verifiable credentials used by INDEX.FILM, the International AI Audiovisual Asset Registry, to give digital works — films, series, episodes, characters, workflows and worlds — a permanent and independently verifiable identity.

INDEX records registration facts and verification scope, supporting the recognition of rights worldwide. Every statement in an INDEX record names the party that made it, the basis on which it was made and the time at which it was recorded.

The key words MUST, SHOULD and MAY in this document are to be interpreted as described in IETF BCP 14.

02Terms and parties

PartyDescription
RegistryINDEX.FILM. Maintains this Standard, assigns INDEX IDs, keeps the authoritative register, signs registration facts and operates public verification.
RegistrarAn accredited organisation that registers works for registrants, binds content fingerprints and issues verification credentials under its own identity.
IssuerAny party that signs a credential about a work: the Registry, accredited registrars, accredited law firms and festivals.
RegistrantThe party that declares a work through a registrar and is answerable for the declaration.
VerifierAnyone who checks an INDEX ID, record, certificate or credential.

03The INDEX ID

PropertyRule
Length10 characters
Alphabet23456789ABCDEFGHJKMNPQRSTUVWXYZ — 31 symbols, excluding 0, 1, I, L and O
CaseCase-insensitive; stored and displayed in upper case
DisplayGrouped 4-4-2 in a monospaced face: 7K3P 9Q2M 4X
Links and QR codesWritten continuously: index.film/7K3P9Q2M4X
Canonical IRIhttps://index.film/{ID}
AssignmentRandom. An INDEX ID carries no year, category or registrar information and is never reused.

Check character

INDEX IDs assigned by the Registry end with a check character. With symbol values v₁…v₁₀ taken from their positions in the alphabet, the sum of i × vᵢ for i = 1…10 MUST be divisible by 31. Because 31 is prime, every single-character error and every transposition of adjacent characters is detected.

Identifiers issued before the Registry opened remain valid exactly as issued. Verifiers MUST NOT reject such an identifier for lacking a check character.

Input tolerance

Implementations SHOULD remove spaces, hyphens and dots and convert input to upper case before parsing. Characters outside the alphabet SHOULD be treated as possible typing errors and answered with candidate identifiers; they MUST NOT be silently replaced.

Earlier identifiers

Earlier long-form identifiers, such as IXF-AIF-2026-{ID}, resolve permanently to the same record.

04Permanent addresses

The following addresses are printed on certificates, posters and end cards. Once published they remain valid permanently.

AddressContent
https://index.film/{ID}Work record (HTML with JSON-LD)
https://index.film/{ID}.jsonPublic record (JSON-LD)
https://index.film/{ID}/v/{n}Record version n
https://index.film/verify/{ID}?v={n}Verification of certificate version n — the target of every certificate QR code
https://index.film/d/{number}Public summary of a certificate or schedule
https://index.film/.well-known/did.jsonRegistry DID document
https://index.film/ns/v1INDEX JSON-LD vocabulary
https://index.film/status/{list}Credential status lists
https://api.index.film/v1/…Registry API, described by the OpenAPI contract

05The record

An INDEX record describes one work. Each public field states its source: declared by the registrant, or verified by a named issuer. A verified field that is later changed returns to declared.

FieldRequired fromNotes
id, aliasesCreationCanonical INDEX ID and earlier identifiers
workType, formTypeCreation / BOUNDfilm, series, episode, character, workflow, world; feature, short, series, episode and others
title.original, title.originalLanguage, title.translationsCreation / BOUNDOriginal spelling preserved; languages tagged with BCP 47
logline, productionYear, durationSeconds— / BOUNDLogline up to 500 characters
originalLanguages, countries, genres, creditsBOUND / —Countries as ISO 3166-1; up to 30 credits
rightsHolder.nameCreationShown as the registrant-declared rights holder
rightsHolder.legalName, jurisdiction, registrationNumber / LEI / ISNIVERIFIEDAt least one organisational identifier
aiDisclosureCreation / BOUNDSummary, generated imagery, synthetic performers, synthetic voice, real-person likeness, tools
aiUsePolicy—Training, fine-tuning, style or character reference, voice or likeness: permitted, reserved or by agreement
assets[]BOUNDRole, SHA-256, ISCC, size, media type and cut
externalIds, relations—EIDR, ISAN, IMDb, festival submission numbers; series, adaptation and derivative relations
level, status, version, versionHash, timestampSystemSee clauses 6 and 9
registrar, attestations, currentDocumentSystemIssuing parties and current certificate

06Assurance levels

Assurance levels only increase. Each level is represented by a seal from the INDEX.FILM visual identity.

LevelColourRequirementGranted byDocument
Registered—INDEX ID and core fieldsRegistrar submissionRecord page
BOUND#B13D36At least one master or screener SHA-256 bound and BOUND fields completeRegistrar submissionCertificate of Registration
VERIFIED#D7AA12A verification credential covering at least the rights holder's identity and the registrant's authorityAccredited registrarCertificate of Registration (re-issued)
CLEARED#216947A rights clearance conclusion with territory, media, term and conditionsAccredited law firmCertificate of Registration and Rights Clearance Schedule

Seal statements

  • BOUND — Submitted files are bound to the record. The registrant's declarations are published with it.
  • VERIFIED — The verifier, basis, date and items checked are listed in the record.
  • CLEARED — Legal opinion, territory, media, term and conditions are documented in a rights clearance schedule.

07Documents

DocumentFormatNumberIssuer
Certificate of RegistrationA4 portraitIC-{ID}-{nn}Registry, with the submitting registrar
Rights Clearance ScheduleA4 portraitRS-{ID}-A{nn}Accredited law firm
Certificate of HonourA4 landscapeAssigned by the festivalFestival, carrying the INDEX verification strip
  • A Certificate of Registration is issued from level BOUND, once content fingerprints are bound.
  • Each work has one current Certificate of Registration. A change of level issues a new version; earlier versions keep their signatures and verify as updated by a newer version.
  • Every certificate carries a QR code to index.film/verify/{ID}?v={n} (error correction level Q, printed at 22 mm or larger) and embeds its signed credential.
  • Every certificate is issued in English, the reference edition, together with an edition in the official language of the jurisdiction concerned: the rights holder's jurisdiction, failing that the first country of production, failing that the sponsoring registrar's country. Where that language is English, the certificate is issued in English only.
  • Editions are available in eleven languages: English, French, German, Spanish, Portuguese, Simplified Chinese, Traditional Chinese, Japanese, Korean, Thai and Arabic. A registrar may request further editions at any time. All editions of a certificate share one certificate number, one QR code and one signed credential; where editions differ, the English edition prevails.
  • Arabic text runs right to left; identifiers, domains and hashes run left to right. Titles keep their original spelling and script in every edition.
  • Certificates are titled “Certificate of Registration” and carry the statement: “This certificate attests the registration facts and verification scope listed, supporting the recognition of rights worldwide. The live record at index.film is authoritative.”

08Verifiable credentials

CredentialIssuerPrincipal claims
RegistrationCredentialdid:web:index.filmINDEX ID, title, declared rights holder, content fingerprints, registrar, registration time, record version hash
VerificationCredentialRegistrar DIDVerification scope, basis, verifier reference, date, evidence hash references
ClearanceCredentialLaw firm DIDConclusion, scope of review, territory, media, term, exclusions, counsel and opinion reference
HonourCredentialFestival DIDEdition, section, honour, recipient, citation and decision reference
  • Credentials conform to the W3C Verifiable Credentials Data Model 2.0.
  • Proofs are DataIntegrityProof with the eddsa-jcs-2022 cryptosuite (Ed25519, RFC 8032; JSON canonicalised with RFC 8785).
  • Each credential carries credentialStatus entries of type BitstringStatusListEntry for revocation and suspension.
  • The credential subject is https://index.film/{ID}. Issuers are identified by did:web.

09Versions and evidence

Every change to a record creates a new version. The version content is canonicalised with RFC 8785 and hashed with SHA-256 (FIPS 180-4) to produce versionHash, which includes the hash of the previous version and so forms a hash chain.

Each versionHash is time-stamped by a trusted time-stamping authority under RFC 3161. The time-stamp token is published with the version and can be verified with standard tools.

versionHash = SHA-256( JCS( { indexId, iri, registrar, version, level, status,
                          record, registrantRefHash, assets, previousVersionHash, recordedAt } ) )

10Content fingerprints

  • A SHA-256 digest is required for every bound file. An ISCC code (ISO 24138) MAY be added to support discovery of copies across formats.
  • File roles: master, screener, trailer, poster, still, subtitle, audio, project_file, other.
  • The Registry receives fingerprints only. Files remain with the registrant or registrar.
  • A master fingerprint belongs to one work.
  • Fingerprints may be retired; retired fingerprints remain in the record history.

11Verification

Anyone can verify an INDEX ID, a certificate number or a content fingerprint at index.film/verify or through the public API. A verification response states one of the following results:

ResultMeaning
Valid certificateThe certificate is the current version for the work.
Updated by a newer versionA newer certificate has been issued; its number is given.
Being issuedThe certificate is being prepared.
Under reviewThe registry is reviewing a rights matter and publishes the outcome on the record.
WithdrawnThe record has been withdrawn following registry review.

Signatures, status lists and time-stamps can also be checked offline with any implementation of the referenced specifications.

12Privacy

  • The Registry stores an opaque registrant reference supplied by the registrar, not the registrant's personal contact details.
  • Verification materials, contracts and consents enter the Registry as hash references; originals remain with the issuing party.
  • Public pages show only the fields marked public in clause 5. For individual rights holders, only the name is published.

13Normative references

  • W3C — Verifiable Credentials Data Model v2.0
  • W3C — Decentralized Identifiers (DIDs) v1.0; did:web method
  • W3C — Data Integrity EdDSA Cryptosuites v1.0 (eddsa-jcs-2022)
  • W3C — Bitstring Status List v1.0
  • W3C — JSON-LD 1.1
  • IETF — RFC 3161 Time-Stamp Protocol
  • IETF — RFC 8785 JSON Canonicalization Scheme
  • IETF — RFC 8032 Edwards-Curve Digital Signature Algorithm
  • IETF — RFC 9457 Problem Details for HTTP APIs
  • IETF — BCP 14 Key words; BCP 47 Tags for Identifying Languages
  • NIST — FIPS 180-4 Secure Hash Standard
  • ISO — ISO 24138 International Standard Content Code; ISO 3166-1 Country codes
  • OpenAPI Initiative — OpenAPI Specification 3.1
Standards implemented15
W3CRecommendation
Verifiable Credentials Data Model
v2.0
Implemented in INDEXRegistrations, verifications and clearances are issued as verifiable credentials.
W3CRecommendation
Decentralized Identifiers
DID v1.0 · did:web
Implemented in INDEXRegistry and issuer identities are published as did:web documents.
W3CRecommendation
Data Integrity EdDSA Cryptosuites
eddsa-jcs-2022
Implemented in INDEXCredentials are signed with Ed25519 using the eddsa-jcs-2022 cryptosuite.
W3CRecommendation
Bitstring Status List
v1.0
Implemented in INDEXCredential status is published in privacy-preserving status lists.
IETFRFC
Time-Stamp Protocol
RFC 3161
Implemented in INDEXEvery record version carries a trusted time-stamp.
IETFRFC
JSON Canonicalization Scheme
RFC 8785
Implemented in INDEXRecord versions are canonicalised and hashed into reproducible evidence.
IETFRFC
Edwards-Curve Digital Signatures
RFC 8032 · Ed25519
Implemented in INDEXEd25519 digital signatures protect every credential.
NISTFIPS
Secure Hash Standard
FIPS 180-4 · SHA-256
Implemented in INDEXContent fingerprints identify the exact files of a work.
ISOInternational Standard
International Standard Content Code
ISO 24138 · ISCC
Implemented in INDEXContent codes support discovery of copies across formats.
W3CRecommendation
JSON-LD
1.1 · schema.org
Implemented in INDEXRecords are published as linked data for search engines and AI agents.
OpenAPI InitiativeSpecification
OpenAPI Specification
3.1
Implemented in INDEXOne open API contract serves every accredited registrar.
IETFRFC
Problem Details for HTTP APIs
RFC 9457
Implemented in INDEXConsistent, machine-readable responses for every integration.
ISOInternational Standard
Country Codes
ISO 3166-1
Implemented in INDEXTerritories and jurisdictions use ISO 3166 codes.
IETFBest Current Practice
Tags for Identifying Languages
BCP 47
Implemented in INDEXTitles and languages are tagged with BCP 47.
EIDR · ISANIndustry identifiers
Entertainment Identifier Registry · ISAN
externalIds
Implemented in INDEXRecords can reference EIDR and ISAN identifiers of the same work.
Applications

Join the global registry network.

INDEX Standard 1.0 · INDEX.FILM