> For the complete documentation index, see [llms.txt](https://docs.usd.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usd.ai/depositor/faq/gpu-loans.md).

# GPU Loans

How USD.AI GPU-backed loans work, what collateral is accepted, how loans are underwritten, and how depositors are protected if a borrower defaults.

For a full protocol walkthrough, see [How USD.AI works](/usdai/how-it-works.md).

<details>

<summary>How many loans are live?</summary>

You can check can the status of all the loans on the “Reserves” page of the USD.AI app <https://app.usd.ai/reserves>

</details>

<details>

<summary>Why aren't there more loans?</summary>

The loan process can take as little as a few days or as long as a few months depending on its complexity and in these early stages, the protocol is being more prudent to ensure users and USD.AI is not negatively impacted.

The 2 main stages of a loan are:

1. Underwriting = evaluating business, assets, legal, etc
2. Install = receiving hardware, installing, verifying

If you're evaluating the borrower side, start with the [Borrower overview](/borrower/overview.md).

</details>

<details>

<summary>GPUs depreciate fast. How is that risk handled?</summary>

See [Risks & Mitigants](/usdai/risks-and-mitigants.md) section

</details>


---

# 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.usd.ai/depositor/faq/gpu-loans.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.