# Get started

To get started with MEVerse, let's study basic words related to MEVerse first!

* **MEV :** Native coin in MEVerse mainnet
* [**MEVerse Dex**](https://meversedex.io/) **:** MEVerse DEX is a representative DeFi(Decentralized Finance) protocol based on MEVerse mainnet network. MEVerse DEX supports AMM(Automated Market Maker) swap, IMO(Initial MEVerse Offering), and NFT Marketplace of the Entertainment-focused MApps(MEVerse DApp) tokens. MEVerse Bridge also supports network conversion of assets on various networks.&#x20;
* [**MEVerse Bridge**](https://www.meversebridge.io/) **:** MEVerse Bridge is a cross-chain service that supports the network conversion of assets on various networks. MEVerse Bridge currently supports Ethereum, Binance Smart Chain, Polygon, Klaytn, and Tomochain. MEVerse Bridge will play a key role in building MEVerse ecosystem.
* [**MEVerse Scan**](https://www.meversescan.io/) **:** MEVerse scan allows users to access different details related to transactions on specific wallet addresses and blockchains including amount transacted, sources and destination of funds, and status of the transactions.
* [**Meta Mask**](https://metamask.io/) : MetaMask is a free web and mobile crypto wallet that allows users to store and swap cryptocurrencies, interact with the Ethereum blockchain ecosystem, and host a growing array of decentralized applications (dApps). It is one of the most widely used crypto applications in the world.

> Since MEV is required to deploy smart contract or to make transactions, this guide uses **MEVerse Testnet**.


---

# Agent Instructions: 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:

```
GET https://meversedex.gitbook.io/meverse-dev-docs/get-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
