> For the complete documentation index, see [llms.txt](https://guides.upland.me/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.upland.me/getting-started/join-and-create/layer-2-developers.md).

# Layer 2 Developers

The Upland City-Builder empowers developers to create **Layer 2 experiences** through the **Upland** [**Developer Network (UDN)** and **UDN Pro**](https://www.upland.me/events/the-upland-developers-network). These tools allow you to integrate third-party applications and Upland assets like properties, block explorers, and cars into your creations, no Web3 or blockchain expertise required.

With UDN, developers of all backgrounds, from 2D to VR, can design games, token-gated experiences, and more. Layer 2 unlocks the ability to give players ownership of in-game assets they earn, creating immersive and innovative possibilities.

Ready to build? UDN provides tools, documentation, and community support to help you bring your ideas to life. Check out the Developer Hub: <https://docs.developers.upland.me/upland-developers>.&#x20;

Watch the video below to explore how Layer 2 works and see examples of real-world applications. Start shaping the Upland Metaverse today!

{% embed url="<https://youtu.be/DYeudsn5TDg?si=6bOrg8aDvJAjLTkT>" %}


---

# 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://guides.upland.me/getting-started/join-and-create/layer-2-developers.md?ask=<question>&goal=<user_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.