# Protocol Metadata

Liquid Collective protocol smart contracts expose a metadata URI that resolves to an IPFS directory containing resource files about the protocol.

Metadata directory contains different public resources such as:

* Protocol Terms & Conditions
* Marketing resources such as Liquid Collective logo pack
* Security Audits reports
* etc.

Any user can access the metadata by getting the IPFS URI from the River smart contracts and then retrieving the metadata directory from IPFS.

Below is an example of an RPC call to get Liquid Collective metadata URI using [cast](https://book.getfoundry.sh/cast/)

```
$ cast call 0x8c1BEd5b9a0928467c9B1341Da1D7BD5e10b6549 "getMetadataURI()(string)"
ipfs://QmZrpoUUKZ2n5Pd3EAG38HRHjNh66MRBFMMBqsFUVS6NpB
```


---

# Agent Instructions: 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.liquidcollective.io/eth/overview/protocol-metadata.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.