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

# Abstract

## Abstract

GoFi Cash turns the stablecoins in your wallet into things you can use: travel eSIM data, virtual phone numbers and a prepaid card. You connect a wallet, pick what you need and pay. No bank account, no exchange account, and GoFi never holds your crypto.

The product is live at [gofi.cash](https://www.gofi.cash/) and takes USDC on Solana and USDG on Robinhood Chain. GoFi earns a margin on every order, so the business does not depend on a token.

The GOFI token, planned for a later phase, adds a membership layer on top. Holders and stakers unlock discounts and free plans, can pay for services in GOFI, and 25% of monthly revenue goes to buying back and burning the token.


---

# 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://docs.gofi.cash/readme.md?ask=<question>&goal=<user_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.