> For the complete documentation index, see [llms.txt](https://usdfuel-experiment.gitbook.io/the-usdfuel-manifesto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usdfuel-experiment.gitbook.io/the-usdfuel-manifesto/the-usdfuel-manifesto.md). # The $FUEL Manifesto ### Borrow attention. Amplify it. Return it as fuel. $FUEL is an experimental meme project built around attention, fees, and respect. Meme coins are not driven by fundamentals first. They are driven by attention. Liquidity follows attention.\ Volume follows attention.\ Narratives follow attention. $FUEL exists to test a different model. Instead of chasing attention through distortion, we want to borrow a spark from resilient meme communities, amplify it, and return it as fuel. This is not only a token. It is an arena where meme communities compete for the next ignition. **Find the next phoenix before the chart wakes up.** Version: v0.1 — Experimental Draft This document will evolve with the community. Official X : CA：TBA --- # 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://usdfuel-experiment.gitbook.io/the-usdfuel-manifesto/the-usdfuel-manifesto.md?ask=&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.