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

# Spending limits

> Let an AI app or GOL chat send USDC within limits you approve on Base or Solana devnet.

A spending limit, technically a mandate, gives a named agent permission to perform specific actions within the signed bounds. The contract enforces the applicable asset, recipient, per-action and total amounts, expiry and paused or revoked state. It does not guarantee a profit or that an offchain trading strategy is safe.

The private app supports owner-approved USDC spending limits on three networks. Public access remains closed.

| Network | Money | Wallet | Network fees |
| - | - | - | - |
| Base mainnet | Real USDC | An EVM wallet such as MetaMask | The agent needs ETH for gas, supplied separately from your USDC. |
| Base Sepolia | Test USDC | An EVM wallet such as MetaMask | The agent needs test ETH for gas. |
| Solana devnet | Test USDC | A Solana wallet with devnet support, such as Phantom or Solflare | You pay devnet SOL for setup and safety transactions. GOL's devnet relayer pays each transfer's fee and is reimbursed from a separate USDC fee limit, including for refused transfers. |

Open **Spending limits** and choose the network. Solana owners start on Solana devnet. Switching networks moves no funds and you can switch back. Use the demonstration on the page to compare an allowed request with a refused above-limit request without moving money; it explains the checks and is not evidence of a live transaction.

> [!NOTE]
>
> Wallet and device testing is incomplete. Check the network, recipient and
> amounts in your wallet before signing. For a test, use a disposable wallet on
> Base Sepolia or Solana devnet, not your main wallet. The Solana devnet
> programs are unaudited.

## Who can use a spending limit

Each spending limit belongs to one connection: an AI app connected through [Connections](https://docs.gol.network/app/connections.md) with execution permission for the selected network, or GOL chat. Inside the signed recipient, amounts and expiry, that agent can send USDC without asking you again. Creating, pausing, resuming and revoking a limit always need your wallet.

To use a Solana devnet limit from an AI app, connect the app with your Solana wallet and allow Solana devnet when it asks for consent. A connection signed in with a Base wallet cannot use a Solana limit, and the reverse also applies.

## Create one on Base

**1. Approve a wallet spending cap**

Under **Wallet spending cap**, enter the amount and approve it in your wallet. The cap is a token allowance shared by every spending limit using the same contract, so changing it affects their available spending. Replacing a nonzero cap first resets it to zero, with a wallet confirmation for each transaction. Your USDC stays in your wallet. **Remove token allowance** sets the cap back to zero.

**2. Choose the connection and terms**

Under **Create an MCP mandate**, select the connection, enter the allowed recipient and the per-transfer amount, and choose an expiry from 1 to 30 days. The limit's total is the cap you approved.

**3. Review and sign**

Select **Review and sign mandate** and confirm in your wallet.

## Create one on Solana devnet

**1. Choose the connection and terms**

Under **Create a Solana devnet mandate**, select the connection, then enter one allowed recipient other than yourself, the per-transfer amount, the total and an expiry from 1 to 30 days.

**2. Prepare and check**

Select **Prepare and check**. The app verifies both setup transactions and simulates them on devnet, then shows the amounts, expiry, recipient, agent, maximum network fees and the token approval.

**3. Sign once**

Select **Sign both setup transactions**. Your wallet signs both transactions in one prompt. If creation fails after the first transaction lands, revoke or reuse that grant before starting again.

Devnet SOL and test USDC come from public faucets.

## Let GOL chat spend

The **GOL chat** card turns on chat spending for the selected network after one wallet signature over the displayed opt-in text. GOL chat then appears in the connection list like any other AI app, and you create its spending limit the same way.

> [!WARNING]
>
> GOL chat pays without asking each time, only inside the limit's recipient,
> amounts and expiry. Anyone using your signed-in GOL session, or content the
> chat reads, could trigger a payment up to those limits. Set them accordingly.

**Stop GOL chat spending** turns it off without a signature. Chat reports a payment as paid only after its transaction is final.

## Manage your limits

**Your wallet mandates**, or **Your Solana devnet mandates** on Solana devnet, lists each limit with its connection, status, amounts and expiry. Active limits offer **Pause** and **Revoke**; paused limits offer **Resume** and **Revoke**. Confirm each action in your wallet.

Disconnecting an AI app or stopping GOL chat spending ends that connection's payments, but its spending limits stay on chain until you pause or revoke them.

Agent budgets and practice-mode settings are enforced by GOL's server. They are separate from an onchain mandate and do not create one. Review the full wallet approval before authorizing future actions. See [security and control](https://docs.gol.network/app/safety.md) and [Connections](https://docs.gol.network/app/connections.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.