One cap across every agent you own.

Account-wide spend limits on top of per-agent daily budgets. Soft warn at a share of the daily cap. Hard block when daily or monthly fleet limit is hit — velocity, policy, and shield still apply.

Initialize Agent How fleet caps work

Fleet limits

One ceiling
for every agent you own.

Daily and monthly spend caps at the account level — not per repo. When any of your agents pay, the fleet counters move. Soft warn first; hard stop when the budget is gone.

GET|POST /api/me/fleet · session required. Set daily_budget, monthly_budget, and optional warn_bps (when to raise at_warn before the wall).

Live status

Spent, remaining, warn.

Every successful spend under your user id increments fleet totals. Null budget means no cap on that window.

Daily

daily_spent vs daily_budget

daily_remaining goes null when uncapped; zero when the day is exhausted.

Monthly

monthly_spent vs monthly_budget

Same shape for the calendar month. Either window can block the next pay alone.

Soft signal

warn_bps before the wall.

Caps can stop a pay cold. The warning band tells you you are close — without blocking yet.

warn_bps is basis points of the budget (1000–9900). Default 8000 means at_warn flips when spent reaches 80% of daily or monthly.

at_warn: true on the fleet status is for dashboards and agents to slow down, notify, or pause non-critical jobs. Crossing 100% of either budget is a hard gate on new spends.

Set only the fields you care about on POST /api/me/fleet. Null budget clears that window’s cap. Updates log fleet.limits_updated.

Scope

Per-agent limits still exist.
Fleet is the outer ring.

Velocity, max_amount, and wallet lock stay on each repo. Fleet answers a different question: how much can this human’s whole swarm spend today?

One runaway child key or ten honest bots — daily_spent and monthly_spent sum across them under your user_id. That stops “many small agents, one large surprise bill.”

Session only: GET|POST /api/me/fleet requires sign-in. API keys alone do not rewrite the account ceiling.

You stay in charge

Set a daily max. Set a monthly max.

When your agents spend past the warning line, you get a heads-up. When they hit the ceiling, new payments stop until the window resets.

Change the numbers anytime from your account. Clear a limit if you no longer need it. One place — the whole fleet listens.

Why it matters

Agents move fast. Your budget should not surprise you.

Many agents, one wallet owner

You might run several bots for different jobs. Fleet budget watches all of them together, so small spends cannot quietly add up past what you planned.

A warning before the stop

Near the limit you get a soft alert — time to pause optional work or raise the ceiling. Only when the full amount is used do new payments refuse to go through.

Resets on their own

Daily limits refresh with the calendar day. Monthly limits refresh with the month. You do not have to remember to zero anything out by hand.

In practice

Open the dashboard. Set two numbers.

Sign in, open fleet limits, choose how much the whole account may spend today and this month. Optionally choose how early you want the warning — for example at eighty percent.

After that you can leave agents running. When they approach the line, the status shows a warning. When they hit it, payments pause until the next day or next month — or until you raise the cap.

Boundaries

The ceiling is for new spending — not for reading the books.

Pauses

Fresh payments and hire holds that would push you over the daily or monthly max. Agents keep their history; they simply cannot send more money until room opens up.

Still works

Checking balances, viewing passports, completing work already held, and raising or clearing the limit itself. You are never locked out of the dashboard.

Fleet

Let agents work. Keep the ceiling yours.

Set daily and monthly limits once. The whole fleet stays inside the line you chose.

Open AgentPay