You set two caps. Neither can be exceeded by a call, however it was started. Set them at https://agentmore.app/app/budget.
CapWhat it bounds
Per callThe most any single call may cost
Daily budgetThe most every call together may cost in a day
Per call is the one that stops a surprise. Daily is the one that stops a loop.

​
They layer under ours

AgentMore already enforces its own per-call ceiling and daily cap on every account. Your caps sit underneath those. So you can tighten, never raise. Setting your per-call cap higher than ours does not lift anything — the lower of the two is what applies, and that is always the point at which a call is refused.
Start tight. A cap that refuses a call costs you nothing but a retry; a cap set high enough to never trigger is not doing anything.

​
The order of checks

1

The call is priced

The worst case is computed from the input before the request is built. A price shape that cannot be priced from the input is refused here. See How a call is priced.
2

Checked against the per-call cap

Yours or ours, whichever is lower. Over it, the call stops.
3

Checked against today's daily budget

Today’s spend so far is read and this call’s worst case is added to it. If the total would go past the cap, the call stops.
4

Checked against your balance

A call that would take you past your remaining credits stops too. There is no top-up, so an empty balance is a stop until your plan’s credits refresh.
5

The call runs

Only now is anything sent to a vendor.
Every one of those checks happens before the request leaves. There is no point at which a call is half-sent.

​
What a refusal looks like

A refused call is terminal and free:
  • Nothing was sent to any vendor.
  • Nothing was charged.
  • Your agent gets the reason and which cap it hit — not a generic error.
Terminal means it does not retry itself into your cap. The agent stops and tells you. Raise the cap, ask for fewer results, or pick a cheaper tool, and run it again.
That was blocked by my per-call cap — try it with 20 results instead of 200.

​
Seeing blocked calls

On the dashboard, refused calls appear under status codes as Blocked by your limits, and in the call log with the cap that stopped them.
“Blocked by your limits” is always ours, never a vendor’s. A vendor refusing you shows as a failed call — and a failed call is recorded at zero cost as well.
A few blocks is the system working. A wall of them means a cap is set below what your work needs, and the dashboard is the place to see which one.