> For the complete documentation index, see [llms.txt](https://edxalabs.gitbook.io/edxalabs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edxalabs.gitbook.io/edxalabs/edxa-labs/how-it-works.md).

# How It Works ?

![](/files/gPwsppy89LzQ0bJ9E7hk)

Our primary goal is to improve remittance efficiency and reduce cost. 

First thing our partners will need to do is to integrate cryptocurrencies into their existing ecosystem. This can be either EDXA token, or can be their own tokens. If they choose to use their own tokens, EDXA will assist with the integration and deployment until it is available to the market. This will utilize the Launchpad platform. 

Instead of building new tools, we are using existing tools such as wallets and exchanges. We want to ensure the business process is well integrated.

Once integrated, remittance can happen almost instantly anywhere around the world. And much safer as the token holder have absolute control of funds and transactions.

For settlement, we are tapping liquidity from existing exchanges to access other tokens or stable coins. Then is up to the partners how they wish to manage the assets.

#### EDXA Tokens

EDXA tokens will be the native currency around tools and services that being built by EDXA. Some examples, partners can choose to use EDXA as a utility token to facilitate payment for their services. 

If they choose to have their own token, the can use EDXA to mine their own tokens.

#### What does this mean to EDXA token holders ?

For token holders, we foresee there is a potential demand in EDXA. Once the integration is functional, demand will increase and probably increase the token value.


---

# 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://edxalabs.gitbook.io/edxalabs/edxa-labs/how-it-works.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.