01INDEX in acquisition and delivery
Distributors, platforms and broadcasters need to know exactly which work they acquire, which files they receive and how artificial intelligence was used in making it. An INDEX record gives each work a permanent identifier, binds it to exact files by fingerprint, and shows who declared and who verified each fact.
INDEX records registration facts and verification scope, supporting the recognition of rights worldwide. It does not grant rights: the rights you acquire are those in your agreements. A record complements, and does not replace, your contracts, chain-of-title review and delivery requirements.
02Due diligence before acquisition
- Obtain the INDEX ID and the current certificate number from the licensor or sales agent.
- Verify the certificate on the Verify page (index.film/verify): the result should be “Valid certificate” at the level you expect.
- Compare the rights holder in the record with the licensor in your draft agreement, noting whether it is declared or verified and, if verified, by whom and for which scopes.
- Read the AI disclosure and any AI-use policy.
- If the work is CLEARED, compare the Rights Clearance Schedule with the rights you are acquiring.
- Check the record status (active, disputed, revoked or merged) and the version history for recent changes.
- Keep in your file the INDEX ID, record version and certificate number you relied on, and the date of your check.
- State the INDEX ID and the fingerprints of the files to be delivered in the agreement and delivery schedule.
03Reading the record
A record is a set of statements, each with a named source.
| Element | What to look for |
|---|---|
| Field source | “Declared” means stated by the registrant, which is answerable for it; “verified” means confirmed by a named issuer. A verified field that is later changed returns to declared. |
| Attestations | Each verification, clearance and honour shows its issuer, date, basis or scope, and status: valid, suspended or revoked. |
| Verification scopes | Rights holder identity, legal entity, registrant authority, file integrity, AI disclosure review. A scope not listed has not been verified. |
| Versions | Every change creates a numbered, time-stamped version. Earlier versions remain at index.film/{ID}/v/{n}, showing exactly what the record said when you relied on it. |
| Assets | Bound files with role, SHA-256, optional ISCC, size, media type, label and cut version. Retired files remain in the history. |
| Registrar | The sponsoring registrar that manages the record. |
AI disclosure and AI-use policy
The AI disclosure states, with a summary, whether imagery was generated, whether synthetic performers or a synthetic voice appear, the real-person likeness status (none, consented or unspecified) and the tools used. Use it for your own labelling and editorial standards, and check whether an AI disclosure review has been verified. The AI-use policy, where present, marks training, fine-tuning, style or character reference and voice or likeness as allowed, prohibited or negotiable. It records the rights holder’s position and does not itself license or restrict any use; reflect it in your agreement where relevant.
04Reading a Rights Clearance Schedule
A Rights Clearance Schedule (RS-{ID}-A{nn}) records the conclusion of reviewing counsel at an accredited law firm. The firm signs it as a clearance credential, and the record reaches CLEARED.
| Item | How to read it |
|---|---|
| Outcome | Cleared, or cleared with conditions. Conditions are part of the conclusion. |
| Scope of review | The elements reviewed and the cut version. Another cut is not covered. |
| Territory | ISO 3166 country codes, or worldwide. |
| Media | Theatrical, television, SVOD, AVOD, FAST, TVOD, in-flight, hospitality, educational, festival, online short-form or other. |
| Term | Start date and, where stated, end date. |
| Exclusions and conditions | What is not covered, and what the clearance depends on. |
| Reviewing counsel | Name, firm, qualification, jurisdiction and the firm’s opinion reference. |
The schedule is counsel’s statement about the material reviewed. It does not transfer or license rights, and it does not address exploitation beyond its stated territory, media and term.
05Matching delivered files to fingerprints
- In the delivery schedule, specify which delivered files must match which bound fingerprints, by role and cut version.
- On receipt and before any transcoding, compute the SHA-256 of each file with a standard tool such as sha256sum, shasum -a 256 or Get-FileHash.
- Look up each value on the Verify page or with GET api.index.film/v1/public/lookup?sha256={hash}. An exact match identifies the record and the file’s role, and shows whether the file is current or retired.
- Record the results in your delivery acceptance report.
Your own transcodes will have different fingerprints; that is expected. Keep the delivered file and its fingerprint as the reference from which your versions derive. Where an ISCC code is bound, the lookup can also report similar content with a similarity score. A mismatch on a delivered master is a delivery question: ask for the bound file, or for the registrar to bind the file actually delivered.
06External identifiers: ISAN and EIDR
The INDEX ID identifies a work in the INDEX register together with its bound files and attestations. It does not replace the identifiers used in your supply chain.
- ISAN (ISO 15706) and EIDR identifiers, as well as IMDb, TMDB, festival submission numbers and platform addresses, can be recorded as external identifiers.
- External identifiers are declared unless shown as verified; check them in the issuing system where they matter.
- Relations link a record to series, episodes, adaptations and derivative works.
- Map the INDEX ID to your existing identifiers in metadata deliveries and asset management systems.
07Monitoring changes through the API
The public API, documented at index.film/developers, is free to use without a key; rate limits apply.
- For each work you hold, store the INDEX ID and the record version and version hash you relied on.
- Re-read the record periodically with GET api.index.film/v1/public/records/{ID}. A higher version number signals a change; compare it with the earlier version (/versions/{n}).
- On each read, check status and level. Disputed, revoked or merged calls for review.
- Check the credentials you rely on, such as verification and clearance, against the status lists they reference (index.film/status/{list}).
- Before a release, a licence renewal or an onward sale, re-check the certificate with GET api.index.film/v1/public/verify/{ID}.
- Event notifications (webhooks) are sent to accredited registrars for the records they sponsor; other users poll at a frequency proportionate to their needs.
- A merged record points to the surviving record: update your catalogue to its INDEX ID and keep the old one as an alias.
08If a record becomes disputed
A record is publicly flagged as disputed, within two business days, when a complaint under the INDEX Dispute Resolution Policy (IDRP) appears well-founded on its face. The flag is an interim measure, not a decision on rights. Related credentials are suspended, and the Registry may put the issue of new certificates on hold.
- Note the date and the record version at which the flag appeared, and inform your legal and rights teams.
- Contact the licensor and review your warranties, indemnities and notification obligations.
- Decide, under your agreements and applicable law, whether to continue, suspend or adjust exploitation.
- Follow the proceedings: the respondent has 20 days to respond, and the panel decides within 14 days of its appointment, giving reasons. Decisions are published with personal data anonymised.
- Implement the outcome. A dismissed complaint removes the flag; a correction creates a new version; a revoked record remains publicly resolvable with its revoked status and verifies as “Withdrawn”.
The IDRP does not determine copyright ownership with effect against third parties or award damages, and it does not prevent anyone from going to court. If a party shows within the implementation period that it has started court proceedings, the record stays flagged until the court decides.
09Checklist
| Stage | Check |
|---|---|
| Before signature | Certificate valid; rights holder and scopes match the licensor; AI disclosure read; schedule matches the rights acquired; status active |
| In the agreement | INDEX ID, record version, certificate number and file fingerprints stated |
| On delivery | SHA-256 of each delivered file matched to the record |
| During exploitation | Version, status, level and credential status monitored |
| On a dispute | Legal review, contractual steps, outcome implemented |
10Further reading
The INDEX Standard (index.film/standard) defines the record, levels, documents and credentials, and the Glossary (index.film/knowledge/glossary) the terms used here. The developer documentation (index.film/developers) describes the public API. See also the guide for lawyers, financiers and insurers (index.film/knowledge/guides/legal), the white paper on AI disclosure (index.film/knowledge/white-papers/ai-disclosure) and the INDEX Dispute Resolution Policy (index.film/policies/disputes).
This guide is for general information only and does not constitute legal advice.