> For the complete documentation index, see [llms.txt](https://docs.that.global/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.that.global/whitepaper/archive-company-info/what-were-solving.md). # What We're Solving This section outlines key issues that have limited the broader use of digital assets and explains how the Company plans to develop merchant tooling and user-friendly interfaces to support both users and merchants within the crypto community. Each challenge is approached with an emphasis on simplicity, usability, and security. By working on these problems, the Company aims to make the everyday use of digital assets more practical and accessible for people and businesses who independently decide to engage with them. The Company does not guarantee that these efforts will result in widespread adoption, any particular level of usage, or any specific outcome. --- # 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://docs.that.global/whitepaper/archive-company-info/what-were-solving.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.