> For the complete documentation index, see [llms.txt](https://docs.dokidoki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dokidoki.com/resources/for-developers/supported-token-uri-values.md).

# Supported token URI values

## IPFS

If the metadata of your NFT is hosted on IPFS, great! We should be able to get it without any issue, but as there are several ways to write a link to an IPFS resource, we want to make sure yours is included. Our API supports both CID v0 and v1.

The `uri` method of your NFT collection should return:

* ipfs\://{your CID}
* <https://ipfs.io/ipfs/{your> CID}
* /ipfs/{your CID}
* A valid CID directly
* A valid CID path directly

## HTTPS link

If the `uri` method of your NFT collection returns a link to an API, it should be something we can call right away. If you need the link to be concatenated with the token ID or any other kind of processing, contact us.


---

# 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.dokidoki.com/resources/for-developers/supported-token-uri-values.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.