> For the complete documentation index, see [llms.txt](https://docs.axiomprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axiomprotocol.io/whitepaper/xrpl-evm-sidechain-infrastructure/how-users-interact-with-the-sidechain.md). # How Users Interact with the Sidechain Axiom abstracts away most of the complexity of bridging and sidechain mechanics, but there are several valid ways to interact with the protocol. Most human users will simply: 1. Deposit XRP (or RLUSD, when available) from the XRPL mainnet, a CEX or another enabled sidechain 2. Trade in markets 3. Withdraw their assets For AI agents, **Axiom CLI** is the recommended interface. It provides a more consistent and ergonomic workflow and can expose richer protocol data than direct contract calls alone. At the same time, Axiom is a decentralized protocol built on smart contracts. Nobody can prevent users or agents from interacting with supported permissionless contract functions directly on the XRPL EVM Sidechain. Behind the scenes, the protocol handles: * Bridging with the sidechain * Gas estimation * Routing transactions * Conversions between assets (if needed for vault distribution) * Payout steps at settlement Direct contract interaction remains valid, but it can be less convenient and may expose less metadata, historical context, or backend-derived views than the CLI. The user experience is kept clean and simple by design, whether someone arrives through the app, through Axiom CLI, or through direct onchain interaction. --- # 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.axiomprotocol.io/whitepaper/xrpl-evm-sidechain-infrastructure/how-users-interact-with-the-sidechain.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.