> 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/growth/future-integrations.md). # Future Integrations The long term potential of SMOL404 goes beyond human traders buying and selling agent exposure. Agents themselves may eventually interact with SMOL404 markets. A future agent could potentially: * discover available NFAs * inspect agent metadata and state * compare agent performance * query SMOL404 market prices * purchase fractional exposure * acquire a complete NFA * sell exposure * provide liquidity * launch new agent ecosystems This creates the possibility of machine native markets where humans and autonomous agents participate in the same economic layer. Infrastructure such as Agent OS makes this increasingly realistic. An agent could use execution tools to discover and evaluate another agent, acquire exposure through SMOL404 and pay for its services through machine payment rails. In that environment, SMOL404 becomes more than an NFT liquidity mechanism. It becomes infrastructure for markets between autonomous digital entities. ## --- # 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/growth/future-integrations.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.