A global brand may think it has published one product film. In reality, it now controls a small content system: the public master, clean versions, captions, transcripts, alternate languages, product-claim notes, raw footage, audio stems and perhaps 3D source files. Search engines, AI assistants, training crawlers and potential licensees do not use those assets in the same way.
The immediate decision is therefore not whether to “charge AI.” It is which materials should improve discovery, which should be available only under controlled conditions, and which are complete enough—in rights, metadata and delivery—to become licensable production assets.
What changed in the standards layer
IAB Tech Lab finalized version 1 of its Content Monetization Protocol (CoMP) on April 28, 2026. The specification gives content owners and licensed AI systems a shared way to describe a content package, the intended use and the method of access. Its video object can carry language, duration, full-length-versus-clip status, transcript availability, publication status, update date, creation source and provenance information. Intended uses distinguish search, AI training, AI input, indexing and agent activity.
The limitations are just as important. CoMP 1.0 is not a bot-blocking product, a licensing marketplace, a payment clearing house or a reporting system. Commercial terms must already exist outside the API. The protocol can reduce integration friction after a relationship is defined; it does not create demand or revenue by itself.
Really Simple Licensing (RSL) 1.0, published as a Recommendation on December 10, 2025, takes a related route. It provides a machine-readable vocabulary and discovery mechanisms for usage, licensing, payment and legal terms across web pages, images, video, audio and datasets. In July 2026, Cloudflare also separated AI traffic into Search, Agent and Training uses, allowing site owners to manage those categories differently.
These are verified standards and product changes, not proof that the market has converged on one system. They make a more granular strategy possible. They do not settle rights, pricing, buyer demand or enforcement.
A film is one presentation layer over several assets
The public video is only the visible surface. Beneath it sit four types of value: marketing communication, machine-readable product knowledge, reusable production material and claims that need version control.
Opening everything can expose unpublished footage, expiring talent rights or product statements that later become inaccurate. Blocking everything can weaken search discovery, AI citation and pre-sales explanation. A single robots rule cannot decide which shot contains a time-limited certification, which voice track is cleared for synthetic adaptation, or whether a clean plate can be licensed outside the original campaign.
That is why crawler policy should not be delegated entirely to web operations. Marketing owns the customer promise; legal owns the rights position; product teams own claim accuracy; production partners know how the files can be separated and reused.
The practical answer is to establish three asset layers before selecting a technical protocol.
Layer 1: public discovery assets
This layer helps people and systems find and understand the brand. It can include approved campaign films, trailers, product demonstrations, accurate captions, clean transcripts, chapters, product identifiers, languages, publication dates and update dates.
Discovery assets should remain useful when a small excerpt is surfaced out of context. Product identity, use conditions and the date of the information should still be clear. Fast-changing prices, promotions or certification claims should not be baked into evergreen transcripts; they belong in an updateable product or commerce layer.
Brands should also keep provenance separate from access. ONCE’s earlier framework for traceable AI advertising delivery helps answer how an asset was made and changed. A discovery policy answers who may retrieve which version and for what purpose. Both matter, but neither substitutes for the other.
Layer 2: controlled context assets
This layer supports richer machine use without releasing the full production archive. Examples include multilingual transcripts, approved product Q&A, shot-level feature notes, market-specific claim versions, installation steps, service explanations and structured summaries for retrieval or agent workflows.
The key distinction is use. Search indexing, real-time grounding, model training and agent actions are separate activities. A brand might allow material to support search and cited answers while limiting paths, rate, retention or training. Cloudflare’s Content Signals Policy makes a similar separation between search, AI input and AI training, while warning that signals express preferences rather than physically stopping every scraper.
If the business cannot yet identify crawlers, observe traffic or map access to content paths, monitoring should precede monetization. IAB Tech Lab’s bot management guidance also recommends understanding identity, traffic return, content use, infrastructure cost, reputation and strategic value before adopting an allow-all or block-all rule.
Layer 3: licensable production assets
This layer contains material that could be delivered independently under commercial terms: unpublished B-roll, clean plates, isolated product-motion shots, textless masters, audio stems, alternate angles, modular 3D or CG components, outtakes and rights-cleared archive sequences.
Possessing the file is not enough. A licensable asset should pass five questions:
| Decision factor | Question | If the answer is weak |
|---|---|---|
| Discovery value | Does external use help audiences understand or return to the brand? | Keep it internal rather than opening it for fashion’s sake |
| Substitution risk | Could the asset replace the original, reveal a launch or be paired with the wrong brand? | Shorten, watermark for preview or move it behind controlled access |
| Rights completeness | Do talent, music, location, font, third-party product and tool terms cover the intended use? | Exclude it from the catalog until rights are repaired |
| Update liability | Who withdraws or replaces it when specifications, claims or approvals change? | Add an expiry, version and accountable owner |
| Independent deliverability | Does it retain a clear title, language, duration, source and usage note outside the master film? | Add metadata, transcript and preview material |
This is not a licensing score. It is a way to expose gaps that automation cannot repair. The most expensive uncertainty is often not storage but an inability to state what the business is entitled to license.
Add an asset card to the next production brief
CoMP’s video object offers a useful minimum: title, language, duration, full item or clip, transcript status, public or archival status, publication and update dates, author or producer, creation source and provenance availability. A brand still needs commercial fields: rightsholder, permitted uses, prohibited uses, territory, duration, AI-training permission, generative adaptation permission, citation requirement, approver, withdrawal route and contract reference.
That asset card should be accepted with the masters rather than reconstructed by the website team months later. For production companies, it also creates four legitimate service components beyond export counts: rights normalization, transcript and metadata work, package and access design, and version or withdrawal maintenance.
A cost decision can be made without inventing industry averages:
Licensing-readiness cost = rights cleanup + transcript and metadata work + packaging and access + monitoring and updates.
The investment is rational only when the assets have durable discovery value, repeated reuse potential or an identifiable licensing need. Avoided production work, broader distribution and licensing income are hypotheses to test in operations, not guaranteed offsets in the initial budget.
A pilot that does not require building a marketplace
Choose one stable product family with clear rights and likely future reuse. Inventory the published films, transcripts, source footage and derivatives. Assign each item to the public, controlled or licensable layer, then complete asset cards only for the strongest candidates.
Next, bring marketing, legal, web operations and production together to decide how Search, AI Input, Training and human download should differ. Apply monitoring, versioning and withdrawal to this limited set. Expand only when the team can observe genuine discovery, access, maintenance effort or licensing enquiries.
If rights are fragmented, claims change weekly, nobody owns withdrawal, or there is no plausible reuser, the correct next step may simply be a reliable inventory and metadata system. Machine-readable licensing is an operating model, not a button. It amplifies the value of well-prepared assets—and the disorder of poorly governed ones.
Sources
- IAB Tech Lab, CoMP initiative and final version 1 specification, updated April 28, 2026.
- RSL Technical Steering Committee, Really Simple Licensing 1.0 Specification, December 10, 2025.
- Cloudflare, AI traffic options for Search, Agent and Training, July 1, 2026; and Content Signals Policy, September 24, 2025.
