> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/agents/wallets/limits-and-ceilings.md).

# Limits and ceilings

Account caps, balance ceilings, Router allowances, and local run guards bound an agent's spending and execution.

{% hint style="info" %}
Agents is coming soon. This page describes how it works at launch.
{% endhint %}

This page is for owners who want to bound an agent's payments, Router use, balance, and local run.

vAPI agents have account caps, a Router allowance, balance ceilings, and guards inside the local run loop.

## Account spend caps

Account caps apply to every payment from the agent account. Set a limit for one payment and a total for each day:

```bash
vapi accounts caps <name> --per-call <usd> --per-day <usd>
```

The caps also apply when the agent buys Router balance or refills it automatically:

```bash
vapi router buy <1|5|20|50> --account <name>
vapi router buy --auto <tier> --below <usd> --account <name>
```

## Balance ceiling

Each account has a 5 USDC Base ceiling by default. The account sends funds above the ceiling back to its parent, so an agent never holds more than it needs. Set another ceiling, or turn the automatic sweep off:

```bash
vapi accounts caps <name> --ceiling <usd>
vapi accounts caps <name> --ceiling off
```

The per-day cap is the sweep floor. Read [Sending and distributing](/agents/wallets/sending-and-distributing.md#keep-balances-below-the-ceiling) for when sweeps run.

## Daily Router allowance

The owner sets a server-side daily Router allowance on `/link`. The owner can change it later from **My agents** at `/agents`.

The allowance can be from 0 to 1,000 USD. It is the agent's slice of the owner's daily Compute, and the owner's daily Compute remains the total limit.

Check the agent's Compute allowance and Router balance:

```bash
vapi router usage --account <name>
```

## Reference agent guards

Set the reference agent's daily wallet cap, suggested daily Compute allowance, per-call limit, approval threshold, and step limit when you create it:

```bash
vapi agent create <name> \
  --model <id> \
  --instructions <file> \
  --call-budget <usd> \
  --router-budget <usd> \
  --max-per-call <usd> \
  --approve-above <usd> \
  --max-steps <n>
```

By default, the agent asks before a call above $0.50. It uses only verified listings and only listings it found in the same run.

Add unverified listings explicitly:

```bash
vapi agent create <name> \
  --model <id> \
  --instructions <file> \
  --include-unverified
```

The agent stops after 12 model steps by default. It also stops when a budget runs out or a settlement is uncertain. Tool output reaches the model only as untrusted data, and every step is in the audit log.

In the 0.8.0 preview, one run budget caps Call payments and Router top-ups together:

```bash
vapi agent run <name> "<task>" --budget <usd>
```

See each profile, link, and today's Call and Router budgets:

```bash
vapi agent list
```

Pause future runs, then allow them again when you are ready:

```bash
vapi agent pause <name>
vapi agent resume <name>
```

## Next

* [How wallets work](/agents/wallets/how-wallets-work.md)
* [Owner and agents](/agents/control/owner-and-agents.md)
* [Run your first agent](/agents/quickstart.md)

Checked on 2026-10-02.


---

# 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.vapinetwork.ai/agents/wallets/limits-and-ceilings.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.