# Introducing Pixel
Web3 fosters an open and permissionless ecosystem. However, NFT commerce still operates under the old paradigm where each marketplace has fragmented liquidity. Siloed NFT marketplaces not only provide a sub-optimal experience for buyers, sellers and creators, but also restrict the capabilities of an interoperable ecosystem.
Pixel protocol offers aggregated NFT liquidity across marketplaces \[online storefront and front-end will be used as interchangeable terms] built on our ecosystem. Pixel incentivizes community-built storefronts to build NFT applications by splitting the transaction fees between the protocol and the storefronts involved in each transaction.
It introduces a new paradigm by decoupling front-end applications from the underlying liquidity. Anyone can build a front-end application and benefit from having immediate listing liquidity while getting to keep a percentage of transaction fees if any taker or maker orders are created on their application. More details in [Protocol Fees. ](/protocol-fees.md)
While the NFT ecosystem is still relatively nascent, there are thousands of creators, builders and artists creating unique and novel NFT collections with their own mechanics. Users have had to choose between highly liquid marketplaces that have a rigid one-size-fits all user experience or a tailored-made experience with no liquidity. Pixel fixes this bringing the deepest NFT liquidity to the most creative, custom-built front-end applications.
While, the DAO has its own marketplace at [www.pixelgg.com](http://www.pixelgg.com) (more in [DAO-controlled storefronts](/dao-controlled-storefronts.md)), Pixel is a lot more than its own storefront. Pixel serves as the foundation for an ecosystem where frontend builders, both large and small, can monetize the value they create and provide the best user experience. It provides a variety of open-source tools that make it easier than ever for NFT creators or community members to build their own front-end applications (Learn more in Ecosystem Enhancing Modules). \
---
# 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-private.pixelgg.com/introducing-pixel.md?ask=
```
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.