> For the complete documentation index, see [llms.txt](https://docs.liccium.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liccium.com/documentation/about-liccium/introduction/what-is-liccium.md). # What is Liccium? Liccium is software for digital content authentication and rights management, designed for individual creators (Liccium Cloud Application) and media organisations (Liccium B2B Engine). It enables users to digitally sign and declare ownership, rights, and metadata for their content while ensuring that these claims remain verifiable – even if metadata is removed, the file is modified, or the content is shared beyond the creator’s or rightsholder’s control. Instead of embedding metadata, Liccium uses soft binding, linking content to signed declarations stored in federated registries. These registries ensure that ownership claims, rights statements, and licensing information remain discoverable, accessible, and independently verifiable – without relying on a single centralised database or proprietary system. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.liccium.com/documentation/about-liccium/introduction/what-is-liccium.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.