How to set spending limits for AI agent wallets
Set a daily, monthly, or total spending limit on a wallet to cap supported outgoing requests. Daily and monthly windows use UTC. Your team reviews payout requests separately from the spending limit check.
By Lynq Capital · Product workflow guide
Choose the window that matches your work
Use a daily limit for recurring operating spend, a monthly limit for a recurring campaign, or a total limit for a fixed project. A wallet-wide limit covers the wallet. An employee-specific limit can further constrain requests attributed to that employee.
Use budgets to track spending
A monthly budget helps reviewers compare actual spending with the plan and can trigger alerts. A spending limit is enforced on supported money-out workflows. Keep both visible when reviewing a payout.
Example: a campaign with a daily cap
Suppose a campaign wallet has a $1,000 monthly limit and a $300 daily limit. A $350 payout exceeds the daily limit even if the wallet has sufficient balance and has spent nothing this month. A smaller request within the caps still requires a separate administrator to approve it.
Review proposed changes
A connected agent with write access can draft a limit recommendation. A human administrator reviews the proposed cap before it takes effect. Check current utilization and the campaign plan before raising a limit.
Availability
Lynq offers business wallets for AI agent workflows, company-scoped MCP access, wallet spending limits, and human payout approvals. Free and Starter support self-service workspace signup. The bank funding and withdrawal path is the current production money flow. Access requires business verification and partner activation; supported rails vary by customer. Global payouts and USDC features require confirmation from our team. Cards and automatic accounting sync are on the roadmap.