Skip to main content

Budget Requests

Budget requests let an agent ask for a spending budget that a human reviews and approves in the dashboard. Once approved, spend is tracked against the approved amount across standard, x402, and MPP payments. When the budget is exhausted, further payments are blocked.
Budget requests are optional. If no active budget exists for an agent, all payment flows work normally using existing spend limits and policies. When an active budget does exist, both the budget and policies must pass for a payment to go through.

How It Works

Lifecycle

A budget request moves through these customer-facing states: Constraints:
  • One active request per agent at a time
  • Creating another request while one is active returns HTTP 409

SDK API

Create a Budget Request

Parameters: Response (201):
Error (409), active request already exists:

Check Budget Request Status

Query Parameters: Response (200):

MCP Tools

request_budget

Request a spending budget for payments. Submits a request for human approval. Only one active budget request per agent at a time. Applies to all payment types.

get_budget_request

Check status and remaining balance of your budget requests. Use to poll for approval and monitor remaining budget.

Payment Flow Integration

When an active (approved, non-expired) budget exists, every payment flow checks it automatically: Pre-execution (blocking):
  • payments/request: checks budget before policy evaluation
  • payments/approve: checks budget for external wallet payments
  • x402/pre-authorize: checks budget before authorizing x402 payments
  • mpp/pre-authorize: checks budget before authorizing MPP payments
Post-execution (decrement):
  • payments/execute: decrements budget after successful execution
  • x402/record: decrements budget when recording x402 payments
  • mpp/record: decrements budget when recording MPP payments
If a payment would exceed the remaining budget, the authorization response stays customer-facing:

Dashboard

Budget requests appear in the Budgets tab on the Alerts & Approvals page. Requests that need review show:
  • Agent name, purpose, requested amount, category
  • Approve / Reject buttons
  • Optional amount adjustment field (approve a different amount than requested)
Approved requests show:
  • Spend progress bar showing spent and approved amounts
  • Remaining balance and expiry countdown
  • Whether the amount was adjusted from the original request
Completed requests show whether they were declined, expired, or fully used.

Approving a Request

Open the pending request in Alerts & Approvals, review the agent, purpose, amount, and expiry, then choose Approve or Reject. An approver can lower the approved amount or shorten the budget window before confirming.

Audit Trail

Budget requests, review decisions, spend, and expiry are recorded in the organization’s audit history using the same customer-facing labels shown in the dashboard.

Example: Agent Workflow

Next Steps

Payments

Standard payment request and execution

x402 Payments

HTTP 402 micropayment handling

Spend Limits

Configure wallet spend limits

MCP Tools

Full MCP tools reference