> For the complete documentation index, see [llms.txt](https://smol404.gitbook.io/smol404-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smol404.gitbook.io/smol404-docs/intro/what-is-bep-404.md). # What is BEP-404? BEP 404 is the term used by SMOL404 for 404 style implementations deployed on BNB Chain. The idea originates from ERC 404, an experimental architecture that combines fungible token balances with NFT ownership inside the same system. A 404 asset can therefore behave like a regular fungible token while maintaining a corresponding NFT layer. For example: `0.4 TOKEN` The user holds fungible exposure, but no NFT. `1.0 TOKEN` The user holds one complete unit, so one NFT is assigned. `2.0 TOKEN` The user holds two complete units, so two NFTs are assigned. This creates a bridge between two different market structures. The fungible side provides liquidity, fractional ownership and compatibility with token infrastructure. The NFT side preserves unique identity and metadata. SMOL404 applies this concept to BAP 578 agents. --- # 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://smol404.gitbook.io/smol404-docs/intro/what-is-bep-404.md?ask=&goal= ``` `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.