> For the complete documentation index, see [llms.txt](https://docs.rallyprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rallyprotocol.com/react-native-expo/gasless-transactions/getting-started.md).

# Getting Started

## Requirements

This section focuses on enabling gasless transactions on mobile device using natively embedded wallets generated by the [SDK](/react-native-expo/embedded-wallets/getting-started.md). If you would like to utilize gasless transactions on a non-native mobile device such as web app or backend, visit [Using without embedded wallets](/react-native-expo/gasless-transactions/using-without-embedded-wallets.md). 

## Get an API key for gasless transactions

An API key is required to use the infrastructure to power gasless transactions. Visit  <https://app.rallyprotocol.com/> to generate both Amoy and Mainnet Polygon API keys.&#x20;

## Network

This section utilizes Polygon's testnet Amoy network. To switch between Amoy and Mainnet Polygon, update the network config using <https://github.com/rally-dfs/rly-network-mobile-sdk/blob/main/src/network.ts>.

## RLY Token&#x20;

In this section, we leverage the RLY token ([polygonscan](https://polygonscan.com/token/0x76b8D57e5ac6afAc5D415a054453d1DD2c3C0094)) to simplify the developer experience. We maintain a token faucet and manage token contracts to ensure that developers can execute their first gasless transaction without the extra steps.

Once you are ready to use your preferred token on production, refer to the subsequent 'your chosen ERC-20 token' sections.&#x20;


---

# 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.rallyprotocol.com/react-native-expo/gasless-transactions/getting-started.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.