ISCC generation on-premise
Generate content fingerprints on your own infrastructure.
Liccium Engine
Verifiable declarations across your entire catalogue
Large media organisations, tech platforms, and AI providers use the Liccium B2B Declaration Engine to sign and publish verifiable content declarations at catalogue scale – on their own infrastructure, integrated with existing workflows.
Liccium Engine
What Liccium Engine offers media organisations
Open, federated content registries
Publish declarations anyone can resolve and verify.
Binding of machine-readable rights and metadata
Rights and metadata bound to each asset’s fingerprint.
Liccium plugins for each use case
Add only the declarations each workflow needs.
Solutions for each media sector
Tailored to each sector’s metadata and rights
Image
Stock photo platforms, photo licensing agencies, news publishers …
Audio
Record labels, music publishers, digital distributors for music and audiobooks …
Text
Academic, trade, educational, news, and audiobook publishers, literary agencies …
Video
TV broadcasters, video producers and distributors …
Use cases
What organisations do with Liccium
AI preferences
Declare how your catalogue may be used for AI training. Reservations are machine-readable and bound to each asset’s content fingerprint, so AI developers can read and act on them.
AI content licensing
Offer your catalogue as licensed training data, under terms expressed in machine-readable form and tied to each content fingerprint.
AI attribution (FAIA)
Provide FAIA flags on each asset – Human-Created, AI-Assisted, or AI-Generated – so downstream users can see whether and how AI was involved.
Verifiable provenance
Establish verifiable provenance for each asset – who created it, who holds the rights, and how it has been declared – so its origin can be independently checked.
How it works
How organisations implement Liccium
Generate fingerprints locally
Run the engine on your own infrastructure to generate content fingerprints (ISCC, ISO 24138) directly from your media files. The files never leave your systems.
Select rights and metadata to publish
Choose which rights and metadata to bind to each fingerprint and make publicly accessible.
Obtain a signing certificate or credential
Receive an X.509 certificate from an EU trust service, or a verifiable credential (VC) issued by a trusted service provider, to sign your declarations.
Implement the API and declare
Integrate the Liccium API and publish signed declarations to the federated registries.
Book a personalised demo
See how the Liccium Engine fits your catalogue and existing workflows.