> For the complete documentation index, see [llms.txt](https://docs.likn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.likn.ai/likn-studio/view.md).

# View

<figure><img src="/files/rPRmjv0JvtoOA2ElaELb" alt=""><figcaption><p>Asset viewer</p></figcaption></figure>

UA not only has transaction attributes but also has more rich functions due to the binding of assets. Through the asset binding mechanism, users can comprehensively view and manage their related files, content, rights, and other important information according to different asset types. This deep integration makes each UA a complete digital asset ecosystem, providing holders with all-around asset management and value experience.

UA holders can easily access all content of their bound assets through the platform interface, including detailed asset descriptions, related documents, rights lists, and historical records. This transparent and convenient viewing mechanism not only enhances the credibility of assets but also provides holders with a better asset management experience. Meanwhile, the platform supports the display of multiple content formats, ensuring complete and clear presentation of different types of asset information.


---

# 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:

```
GET https://docs.likn.ai/likn-studio/view.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.