> 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/unity/gasless-transactions/overview.md). # Overview Gasless transactions are facilitated by the [RallyTransact](/unity/getting-started/overview.md#rallyprotocol), functioning as the fully hosted transactions infrastruture for signing, validating, and relaying transactions to the blockchain. RallyTransact removes the requirement for developers to manage nodes, bundlers, and deploy contracts. Additionally, RallyTransact takes care of funding balances for gasless transactions, monitors transactions, and provides enhanced secops. Although RallyMobile provides dev friendly APIs to interact with the transaction infrastructure, RallyTransact can also be used [outside of the SDK](/unity/gasless-transactions/using-without-embedded-wallets.md). Devs can send transactions from their backend, web dapp, desktop, etc and get all the benefits listed above. ### --- # 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/unity/gasless-transactions/overview.md?ask=&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.