> 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/rallyprotocol/gasless-transasctions.md).

# Gasless transasctions

Gasless transactions are a fully hosted transactions infrastruture for signing, validating, and relaying transactions to the blockchain.&#x20;

It removes the requirement for developers to manage nodes, bundlers, and deploy contracts. Additionally, it takes care of funding balances for gasless transactions, monitors transactions, and provides enhanced secops.&#x20;

## With gasless transactions, you can:&#x20;

1. Enable end-users to transfer tokens, claim NFTs, and even deploy smart contracts from within mobile apps gaslessly.
2. Use outside native-mobile environments - developers can send transactions from their backend, web dapp, desktop, etc and get all the benefits listed above.

## Get an API key for gasless transactions

An API key is required to use the gasless transaction infrastructure. Visit  <https://app.rallyprotocol.com/> to generate both Amoy and Mainnet Polygon API keys.&#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 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://docs.rallyprotocol.com/rallyprotocol/gasless-transasctions.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.
