Configuration
Create a completeSPEND_LIMIT policy with its rules in one request:
Rule types
value is always a string, such as "500", or a JSON-encoded object for BUDGET_CAP. A bare number
fails validation. See Budget allocations for BUDGET_CAP
periods and scopes.
How it works
- Per-Transaction: Checked against the requested amount
- Daily/Weekly/Monthly: Checked against cumulative spend + requested amount
BUDGET_CAP and velocity rules use their own transaction
histories, not the combined period counters. See
Budget allocations.
Example evaluation
Wallet-level limits
Set limits on the agent-wallet link when you link it withPOST /api/agents/{agentId}/wallets. To
change them later, send the limit fields without walletId to
PATCH /api/agents/{agentId}/wallets/{walletId}:
- Open the agent detail page.
- On the Overview or Wallets tab, click the pencil icon next to the wallet.
- Update the per-transaction, daily, weekly, or monthly limits and click Save Changes. To
remove a cap, clear the field instead of entering
0.
Auto-creation defaults: When an external wallet is auto-created, Conto applies per-transaction
1,000, weekly 20,000. You can override these when linking a
wallet to an agent. On update,
null removes a cap. A limit of 0 blocks all payments through
that link. Omission on creation applies endpoint defaults (per-transaction 1,000).
Omission on update preserves the existing value. See
Defaults.Tracking spend
Conto tracks spend automatically:- spentToday - Resets at midnight UTC
- spentThisWeek - Resets Monday midnight UTC
- spentThisMonth - Resets 1st of month midnight UTC