> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/contributor/content/collections.md).
# Collections
Collections are groups of [wearables](/contributor/content/entity-types/wearables.md) and [emotes](/contributor/content/entity-types/emotes.md) defined in the same off-chain namespace or on-chain contract.
They are not [entities](https://github.com/decentraland/docs/tree/main/contributor/entities.md) in and of themselves, but their individual items can be obtained from content servers normally using [pointers](https://github.com/decentraland/docs/tree/main/contributor/pointers.md).
### URNs and Pointers
Collections are identified using URNs, which are prefixes to their item URNs. There are 4 general types of URNs:
* `v1` collections with Foundation-approved content (deprecated).
* `v2` collections with community-approved content.
* `thirdparty` collections with items associated to NFTs outside Decentraland.
* `off-chain` collections, containing mostly default items for new avatars.
{% hint style="info" %}
Despite the fact that `v1` collections are deprecated and will not be created or updated anymore, they are still valid and their items can be used.
{% endhint %}
#### Version 1 and 2 Collections
Both the old `v1` and the current `v2` collection namespaces have URNs of the same form:
```
urn:decentraland:::
```
For example:
```
# A collection in the deprecated v1 space:
urn:decentraland:mainnet:collections-v1:DCL Test Masks
# A collection in the v2 community-approved space:
urn:decentraland:matic:collections-v2:0x25a1d66891d44cdf7b8c45802489c1dea7aadf8b
```
If the `:` segment is appended at the end, the URN becomes a [pointer](https://github.com/decentraland/docs/tree/main/contributor/pointers.md) to an item inside the collection. See [wearable pointers](/contributor/content/entity-types/wearables.md#pointers) and [emote pointers](/contributor/content/entity-types/emotes.md#pointers) for information on these.
#### Third-party Collections
Third-party collections, also known as [linked wearables](https://github.com/decentraland/docs/tree/main/contributor/wearables-and-emotes/wearables/linked-wearables.md), are different from regular wearables in that they are tied to existing NFTs outside Decentraland. They allow players to display NFTs from their personal set on their in-world avatars.
Their URNs look like this:
```
urn:decentraland::collections-thirdparty::
```
You can find ample information about these in the [linked wearables](https://github.com/decentraland/docs/tree/main/contributor/wearables-and-emotes/wearables/linked-wearables.md) documentation for creators.
### Discovering Collections
Content servers can give you a list of all known collections, using the [`/lambdas/collections`](https://decentraland.github.io/catalyst-api-specs/#tag/Lambdas/operation/getCollections) endpoint.
The response will be an object with a `collections` property, containing an array of URNs and names. For example:
```json
{
"collections": [
{
"id": "urn:decentraland:amoy:collections-v2:0xff5d4ebc6bc1ff7262cab42d3c693d953f4614d2",
"name": "Winter clothes collection"
},
// ... many more
]
}
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.decentraland.org/contributor/content/collections.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.