> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tythe.finance/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> One account, five capabilities: what each one is, what it needs, and how they fit together.

Tythe's Principal Account is a smart contract on Base that you own. It holds your balance, enforces the mandates you give your agents, draws credit against your Credit Limit, and puts idle capital to work, all from one address and one key. Tythe holds nothing; its role is the code installed on your account. This page is the map of the five capabilities and how they interlock.

### Five capabilities

<CardGroup cols={2}>
  <Card title="Treasury" icon="vault" href="/principals/account/treasury">
    Your operating balance, in your own account, owned by your key. Divided into idle, reserved, and liened. Withdraw idle balance any time.
  </Card>

  <Card title="Payments" icon="money-bill-transfer" href="/principals/account/payments">
    Pay counterparties directly. Let your agents pay per call on x402 through payment sessions your account signs. Every inflow tagged.
  </Card>

  <Card title="Delegate" icon="robot" href="/principals/account/delegate">
    Bind agents. Write mandates with a ceiling on every field. Approve escalations. Revoke at once. Authority that narrows on evidence and never widens past what you set.
  </Card>

  <Card title="Borrow" icon="scale-balanced" href="/principals/account/borrow">
    Fixed-rate, fixed-term Loans against your Credit Limit, drawn by you or by agents within their credit share. Coverage is a lien on your own balance.
  </Card>

  <Card title="Earn" icon="piggy-bank" href="/principals/account/earn">
    Lend to the credit market behind Tythe's first-loss reserve. Save into curated venues you or your agent choose, with Tythe's venue intelligence as the input.
  </Card>
</CardGroup>

### What each one needs

| Capability | Requires                                                                                    | Built or rented                |
| ---------- | ------------------------------------------------------------------------------------------- | ------------------------------ |
| Treasury   | Verification                                                                                | Native, noncustodial           |
| Payments   | Verification; allowlisted counterparties for direct transfers; a mandate for agent payments | Rented rails, native control   |
| Delegate   | Verification; underwriting of each agent                                                    | Native                         |
| Borrow     | Verification; underwriting; the Master Credit Agreement                                     | Native                         |
| Earn: Lend | Verification; the Subscription Agreement                                                    | Native market                  |
| Earn: Save | Verification                                                                                | Curated venues, native control |

### How they interlock

The five capabilities share one balance and one set of rules, so a decision in one shows up in the others.

* **Treasury is the substrate.** Every other capability moves value into, out of, or within it. Idle balance is what Payments spend, what Delegate reserves, what Borrow liens, and what Earn deploys.
* **Delegate reserves; Borrow liens.** A live mandate holds its remaining period budget in reserve so an agent is never starved by a withdrawal. An open Loan holds its lien so Coverage is always there. Both come out of idle, and both are released when the mandate expires or the Loan closes.
* **Borrow is bounded by underwriting and by Delegate.** Your Credit Limit caps outstanding principal; each agent's credit share is a fraction of what is available. A lower limit shrinks agent draws in the same block.
* **Earn is where idle goes when it has nothing else to do.** Lend and Save are explicit instructions from you or an agent with the authority. Nothing is deployed on Tythe's initiative, and a mandate can hold earn authority without holding spend authority.
* **Payments generate the signal.** Revenue-tagged inflows are what capture repays Loans from and what the Intelligence Layer reads to rate you.

### One example

A fund with a principal account holds 500,000 USDC. It binds a research agent with a mandate of 2,000 USDC per day for x402 data purchases, and a treasury agent with earn authority over up to 40% of idle balance across three venues. It draws a 60,000 USDC Loan at a fixed rate to fund a position, pledging 15% of its balance as Coverage under its band. On day one: 60,000 disbursed into the account, a 9,000 lien, a 2,000 reservation, and the treasury agent moves 190,000 into venues. Idle is 500,000 + 60,000 − 9,000 − 2,000 − 190,000 = 359,000, withdrawable at any time by the owner. The research agent pays for data through payment sessions; the fund's revenue lands tagged and capture services the Loan; the Conduct Ratings of both agents move on what they do.

### What the account never does

* Hold your funds anywhere but your own contract.
* Move value without your key or a mandated agent's key.
* Let any agent exceed its effective scope, or let the Intelligence Layer set that scope above the ceiling you wrote.
* Lend, stake, or deploy your idle balance on its own.
* Block your withdrawal of idle balance.

<CardGroup cols={2}>
  <Card title="Operators and keys" icon="key" href="/principals/onboarding/operators-keys">
    Who can sign for the account.
  </Card>

  <Card title="Trust and transparency" icon="shield" href="/get-started/introduction/trust-transparency">
    What is enforced where, and how to verify it.
  </Card>
</CardGroup>
