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

# Top Up

> Two ways to fund the vault — send crypto, or add funds with a card.

The vault pays for everything an agent does. It needs a balance before any paid call can settle. There are two ways to fund it, and an agent can pay as soon as funds settle.

## Send crypto

Open the vault in the console and copy its address for the chain you want to fund. Send USDC (or another supported stablecoin) to that address from any wallet or exchange.

* **EVM address** — Base, Tempo
* **Solana address** — Solana

Funds are usable once the transfer confirms on-chain. No extra step in the console.

## Add funds with a card

For a faster start, the console has **Add funds** — pay with a card and the vault is topped up in stablecoin for you. It is built for quick onboarding and small, frequent payments:

<CardGroup cols={2}>
  <Card title="Quick to start" icon="bolt">
    No lengthy identity checks for everyday amounts. Add funds and your agent can pay within minutes.
  </Card>

  <Card title="Sized for micropayments" icon="coins">
    Up to **\$500 per week**. More than enough for the per-call, sub-cent-to-few-dollar payments agents make.
  </Card>
</CardGroup>

<Steps>
  <Step title="Open Add funds">
    In the console, open the vault and choose **Add funds**.
  </Step>

  <Step title="Pay with a card">
    Enter the amount and pay. The card flow is handled by our payments provider — SAULT never stores your card details.
  </Step>

  <Step title="Vault is topped up">
    The amount lands in the vault as stablecoin. Your agent can pay against it right away.
  </Step>
</Steps>

<Note>
  The weekly card limit is a guardrail for the quick-start flow, not the vault's
  ceiling. To run larger balances, send crypto directly — there is no cap on
  on-chain top-ups.
</Note>

## Watching the balance

An agent can read the vault balance at any time (`sault balance` / `sault_balance`) and check today's spend against its cap (`sault spending` / `sault_spending`). When a paid call fails for lack of funds, the agent gets a clear, structured error to report back rather than retrying blindly.