Budgets · merchant lists · approvals · owner attestation
Agent spend controls
An agent that can pay needs more than a per-payment rule. Agent Trust Cloud keeps a monthly cap per agent, a list of the merchants it may pay, an amount above which a person approves, and a monthly sign-off by the owner — checked against the agent’s own payment record before each payment runs, beside the policy engine, with the stricter answer winning.
The 4 controls
| Control | When it applies | Effect |
|---|---|---|
spend.merchant-allow-list | Only merchants on the agent’s allow-list may be paid | Refused |
spend.monthly-cap | Month-to-date spend may not exceed the agent’s monthly cap | Refused |
spend.owner-attestation | New spend waits for a person until the owner attests last month | Held for a person |
spend.approval-threshold | A payment at or above the threshold needs a person | Held for a person |
The owner’s attestation is a statement generated from the payment record — the count, the total and the merchants — so the owner signs the numbers the product holds rather than typing their own. After a person approves a held payment, the cap and the merchant list are checked again when the agent resumes.
Try it
This agent paid $180 in August and $1,840 so far in September. Change the policy or the payment; the decision is made by the same function the gateway runs.
Held for a person — spend.owner-attestation
The owner has not attested 2026-08 spend, so new payments wait for a person until they do.
$660 left under the cap this month.