> For the complete documentation index, see [llms.txt](https://docs.freespeech.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freespeech.finance/lite-paper/untitled.md).

# Use Case

FreeSpeech.Finance is a cryptocurrency charity that will literally finance free speech.

With big tech and governments increasingly censoring internet users’ expression worldwide, fighting for our fundamental right to free speech has never been more important. And what better way to support that effort than through cryptocurrency, which was designed to be pseudonymous and censorship-resistant.

Other charity tokens such as Sad Cat Token (SCAT) and Kong DeFi (KONG) have had much success generating donations for good causes. Given that our cause involves something important to many in the cryptocurrency community and offers great incentives to holders, we hope word will spread and support will grow. While some may consider SPEECH a meme token, we do not because we take freedom of speech seriously.


---

# 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.freespeech.finance/lite-paper/untitled.md?ask=<question>&goal=<endgoal>
```

`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.
