> For the complete documentation index, see [llms.txt](https://inferra.gitbook.io/inferra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inferra.gitbook.io/inferra-docs/inferra-cloud/renting-compute.md). # Renting compute Renting a GPU on Inferra Cloud takes a few minutes and one signature. You choose a model and a provider, say how many GPU-hours you want, and confirm. Your USDC goes into escrow, and you get an SSH command to a real machine. ### The flow 1. **Pick a model and a provider.** Each model shows its live rate per GPU-hour and the providers offering it, with their region and reliability. 2. **Choose how much.** Enter the number of GPU-hours you want. You see the rate, the compute cost, the protocol fee, and the total before you commit. 3. **Add your key.** Paste the public SSH key you want to use for access. 4. **Confirm.** You sign one transaction, and your USDC moves into escrow. You receive an SSH command and connect to the machine. The protocol fee is 2%. It comes out of the amount on delivery, so the provider receives the rest and you pay the rate you were quoted. ### Rent now, or hold for later You can take a machine immediately, or you can buy the hours and hold them as a claim to redeem whenever you need them. Held hours stay yours, with the USDC safe in escrow until you decide to use them. ### Managing your rentals Your account keeps track of both states of a rental. * **In escrow.** Compute you have paid for but not yet started. The USDC is held on-chain and the hours are yours to redeem at any time. * **Running.** A live machine, with its SSH command ready to copy and a running count of the hours you have used. Usage is metered by the hour. When the hours you bought run out, or after the 30-day term, access ends on its own. There is nothing to tear down and no way to be billed past what you paid for. ### One wallet The same wallet holds your compute, your escrow, and your $INFERRA, whether you are renting here or trading on the terminal. Connect once and everything is in one place. For what happens after you confirm, see [The delivery layer](/inferra-docs/inferra-cloud/the-delivery-layer.md). For the on-chain mechanics that hold your funds, see [The escrow program](/inferra-docs/inferra-cloud/the-escrow-program.md). --- # 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://inferra.gitbook.io/inferra-docs/inferra-cloud/renting-compute.md?ask=&goal= ``` `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.