Scoped budgets

Scoped budgets are the core user experience for paid agent workflows.

Instead of asking the user to approve every tool call, JiesdaPay lets the user approve a bounded scope.

What a scoped budget contains

A scoped budget can include:

• Current task.
• Maximum total spend.
• Per-call maximum.
• Allowed tools or services.
• Time window.
• User identity.
• Organization or project.
• Conditions that trigger re-approval.

The agent can then act inside that boundary.

Why this matters

Without scoped budgets, there are two bad choices:

• Interrupt the user on every paid tool call.
• Give the agent unrestricted payment authority.

Scoped budgets create a middle path: the user makes one clear authorization decision, and the agent can continue working without constant friction.

When to ask again

JiesdaPay should ask for confirmation again when:

• The task budget is exceeded.
• A new paid service is requested.
• The call price is unusually high.
• A sensitive category is involved.
• Enterprise policy requires approval.
• The user or team limit has been reached.

This keeps ordinary work smooth and risky work explicit.

Revocation

Users should be able to revoke active authorization.

Revocation should stop future calls inside that scope. It should not erase historical audit records, because the history is needed for user understanding and financial reconciliation.