> 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/registry-set-up.md).

# Registry Set-up

Liccium’s technology enables third parties to independently set up and operate their own registry nodes within Liccium’s decentralized federated registry infrastructure. This flexible solution serves two key purposes:

## 1. Declaration Registries

Media organizations, membership organizations, or platforms can independently host and manage their own registries to store digital content declarations and rights metadata securely and reliably.

## 2. Verification Registries

Organizations can set up verification nodes to synchronize and access large volumes of rights declaration metadata, enabling rapid, real-time verification of digital media content across decentralized networks.

This federated registry approach ensures:

* **Effective Registry Synchronisation:**\
  Efficient synchronization and interoperability across federated registries, enabling third parties to easily and reliably access extensive declaration data.
* **Flexible, Sector-specific Control:**\
  Organizations can manage and define tailored governance rules, access permissions, and metadata structures, providing customized solutions aligned with specific industry requirements.
* **Scalable Content Authentication:**\
  Supports large-scale deployment and real-time querying, ensuring rapid and secure verification of content provenance and compliance with declared rights and licenses.


---

# 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/registry-set-up.md?ask=<question>&goal=<endgoal>
```

`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.