> For the complete documentation index, see [llms.txt](https://hub.moonexe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.moonexe.com/about-moonexe/mission-and-vision.md).

# Mission & vision

Why MoonExe exists and where we are going.

## Mission

To build the world's most trusted and accessible digital asset exchange platform, and to make cryptocurrency and fiat currency work together seamlessly.

## Vision

To use Web3 technology to support traditional finance by creating a secure, efficient and low-cost exchange infrastructure for fiat currencies and digital assets.

## Learning from technology leaders

The world's most popular transportation company owns no vehicles. The world's largest accommodation provider owns no real estate.

| Company | Market cap | Compared with                              |
| ------- | ---------- | ------------------------------------------ |
| Uber    | US$203 B   | Mercedes and BMW combined: US$150.4 B      |
| Airbnb  | US$75 B    | Marriott, the biggest hotel chain: US$73 B |

Currency exchange is another trillion-dollar industry that is ready for the same kind of change. MoonExe connects the people who have liquidity with the businesses that need it, without holding a bank's balance sheet.


---

# 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://hub.moonexe.com/about-moonexe/mission-and-vision.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.