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

# Ecosystem & Partners

NFTLegends run in Layer 2 ERC721 tokens of Binance Smart Chain & Polygon Network, to be used as a progression within the game and ecosystem of NFTLegends.

![](/files/-Mfx6PHe7cmqciB7-Q4T)

NFTLegends and Polygon Studio are now in close collaboration, to develop NFTLegends in the P2E ecosystem on Polygon.

### **Scalability of the Polygon Network** <a href="#id-8840" id="id-8840"></a>

Polygon is leading the field in Layer-2 solutions, with all the necessary elements to be the key scaling solution leader of Ethereum.

* Growing developer’s community
* High level of decentralization and security
* Lowest gas cost and near-instant transactions

NFTLegends Team is working with many Studio Games and DeFi partners to help expand the NFTLegends' DeFi & NFT ecosystem.

![](/files/-Mfx837PrMiHpWGB2hik)


---

# 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.nftlegends.tech/ecosystem-partners.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.
