Two agents, one limit, one refused.
All guides
Shared limits
Updated
2 min read
by Anlyon Team

Why a timeout still uses your allowance

Understand reserved capacity, consumed impact and unknown exposure before releasing room for another agent action.

unknown outcomesimpact limitsoperations

A refund times out while $30 is reserved for it. Releasing the reservation immediately would let another agent spend that $30, even though the original refund may already exist. An unresolved operation must continue to count against available capacity.

Anlyon reports consumed impact, reservations and unknown exposure for applicable impact limits. Unknown outcomes keep their allowance held until settled. A read-back that finds nothing does not, by itself, establish that the operation failed.

Read the capacity as evidence

Consider a $100 daily allowance with $40 already consumed, a $20 pending operation and a $30 uncertain refund. Only $10 is uncommitted in this illustrative accounting. The uncertain refund is not spare capacity simply because the provider did not answer.

StateOperator question
ConsumedWhich completed operations account for this usage?
ReservedWhich admitted operations are still waiting or executing?
Unknown exposureWhich operations may have happened but lack a settled outcome?
AvailableWhat can another applicable operation reserve now?

Use the API's reported availability rather than reconstructing it from cached dashboard totals. Accounting details and applicable scopes belong to the authoritative ledger.

Resolve the cause, not the number

Find the effect and its provider correlation identifier. Inspect the supported read-back evidence. A successful match can settle the effect; an empty search may reflect delayed visibility, a bounded lookup or deleted metadata. Record that uncertainty rather than declaring failure.

If reconciliation exhausts its attempts, an operator may need to resolve the effect using external evidence. A manual resolution remains labelled manual. Increasing the limit is an explicit decision to permit additional exposure, not evidence that the original request failed.

What to tell the agent

Return a structured result saying the operation is unresolved and should not be recreated under a new key. Keep the original business operation identifier in your application. This also prevents a restarted session from treating the request as new work.

Start with the impact-limit fields, then use the unknown-outcome runbook. For the failure mechanism, read what a timed-out API call means.

Continue with a related task

Free tier, no credit card. One command if you use Claude or Cursor.

$ claude mcp add anlyon -- npx -y @anlyonhq/mcp-server