> For the complete documentation index, see [llms.txt](https://docs.baumai.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baumai.xyz/readme.md).

# Introduction

Baum is the agent inside Stable's lender portal — and, with the BAUM token and the Baum Broker collection, an agent that can run your onchain account.

Baum is the agent inside Stable's lender portal. It reviews and verifies mortgage documents, moves loans through funding and onto the Stable Mortgage Registry, and keeps USDX — the stablecoin those loans back — liquid and on peg. It has run Stable's USDX vault for six months; the record is visible on Stable's earn page. Today it works for lenders and brokers. It is the part of Stable that already earns.

These docs are about opening Baum up.

The same agent that runs a lender's pipeline can run an individual's onchain account: hold tokens, provide liquidity, lend, borrow, trade, and vote, from a wallet the user owns, under limits the user sets. The **BAUM token** and the **Baum Broker** collection — 3,888 agent-bound wallets — are how that access is distributed, how the people who use it are rewarded, and how Baum funds its own growth from a mortgage-review tool into a network of agents operating capital across Robinhood Chain.

Every part of the design points at one outcome: **more capital working in USDX, more of it operated by Baum, and the rewards going to the people who put it there.**

## Where to start

| If you want to…                | Read                                                                                                 |
| ------------------------------ | ---------------------------------------------------------------------------------------------------- |
| Understand the tokens involved | [Token overview](/tokens/tokens.md)                                                                  |
| Get a Broker                   | [Mint](/baum-brokers/mint.md) and [Broker vault](/baum-brokers/vault.md)                             |
| Put a Broker to work           | [Activation](/baum-brokers/activation.md) and [Baum Portal](/baum-portal/portal.md)                  |
| Earn points and level up       | [Earning points](/points-and-levels/points-and-levels.md) and [Levels](/points-and-levels/levels.md) |
| Lend USDG                      | [USDX lending market](/network/lending-market.md)                                                    |
| Govern a sub-DAO               | [Sub-DAOs](/network/sub-daos.md)                                                                     |
| See what's shipping when       | [Schedule](/reference/schedule.md)                                                                   |

## Links

* Website: [baumai.xyz](https://baumai.xyz)
* X: [@baumreview](https://x.com/baumreview)
* Whitepaper (v0.1): [Stable-Finance/baum-whitepaper](https://github.com/Stable-Finance/baum-whitepaper)

{% hint style="info" %}
Broker points and sub-DAO allocations are program rewards for network participation. Nothing in these docs is financial advice.
{% endhint %}


---

# 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.baumai.xyz/readme.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.