> For the complete documentation index, see [llms.txt](https://metapath.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metapath.gitbook.io/docs/about-metapath.md). # About MetaPath MetaPath is the leading and most-efficient decentralized finance platform in the universe. MetaPath is the pioneer and first cross-metaverse, cross-chain. We are building two products – one is a platform called MetaPath platform and the other one is a protocol called Metapath Protocol. We have already built a MetaPath platform which will be a one-stop shop that will enable users to find the best route to exchange all crypto-related assets including fungible in the metaverse. Initially, we will use API to connect them; in Phase II, we will use a new product called MetaPath Protocol. It is a blockchain asset routing protocol which aggregates not only cross-chain bridges. The goal of the MetaPath team is to realize the interconnectivity of blockchain ecosystems where users can reliably swap or transfer any digital asset and get paid for every transaction. Support: --- # 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://metapath.gitbook.io/docs/about-metapath.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.