> For the complete documentation index, see [llms.txt](https://whitepaper.pepperbird.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.pepperbird.finance/features/driving-utilization.md). # Driving Utilization Building utilization for PepperBird Token is vital because it helps drive everything else behind the scene. While enabling gasless transactions is one stop on our utilization roadmap, it is not the only component of the systems we are building. PepperBird Finance is built around merging the management of fiat and crypto wealth under one umbrella. Our core strength is building applications, utilizing advances in software technology, simplifying processes and developing APIs. Pepperbird Marketplace for developers - APIs developed and tested, made available via our marketplace. We are not competition, we are innovators, with this in mind, $Pepperbird serves as a gateway to accessing an Ecosystem built around use probabilities with special offers to incentivized utilization. --- # 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://whitepaper.pepperbird.finance/features/driving-utilization.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.