1Password debuts AI Spend and Consumption Management inside SaaS Manager to address token-based cost visibility for enterprise AI

1Password launched AI Spend and Consumption Management, a new capability inside its SaaS Manager platform that gives IT and finance teams a unified, real-time view of how their organizations consume and spend on AI services from vendors including Anthropic, Cursor, and OpenAI. For AI builders and teams managing agentic workflows, this signals a growing move toward FinOps-style visibility for token-based AI costs.

What happened

The feature connects directly to vendor admin APIs to pull token-level consumption data daily and normalizes it across providers into a single dashboard. Organizations can set vendor-level spend limits, configure threshold-based alerts via Slack and email, and break down usage by team, user, vendor, and model. The system also captures consumption at the API level regardless of whether a human or an AI agent generated it.

The capability is now in public preview and requires no separate add-on fee for existing SaaS Manager customers. Broad availability is planned for fall 2026.

1Password CFO Greg Henry described the challenge: "Developers are consuming tokens at a pace that traditional budgets weren't built to manage, and IT and finance teams are being asked to forecast and justify AI investments without a clear view of what's actually driving costs."

Why AI builders should care

Token-based pricing is fundamentally different from per-seat SaaS. A single engineering team running agentic workflows can burn through a prepaid budget in weeks. Without visibility, overspend shows up on the invoice months later.

For AI builders deploying products that rely on models like Claude, GPT-5.6, or Cursor, this is a preview of how enterprise procurement expects AI costs to be managed. The FinOps Foundation reported that 98% of organizations now actively manage AI costs, up from just 31% in 2024. Knowing which models and vendors drive spend helps teams forecast costs, justify budget, and choose the right model for the job.

Practical implications

The feature disaggregates consumption by team, user, vendor, and model. That means a CFO can see whether one team's heavy Claude usage powers a revenue-driving feature while another team's OpenAI spend funds low-value automation. Henry emphasized that high token consumption isn't automatically waste: "What matters is whether that consumption is producing enough business value to justify the spend."

Agent-level visibility matters because autonomous AI systems can generate runaway costs in ways humans cannot. An agentic coding assistant stuck in a retry loop can consume thousands of dollars in tokens in minutes. 1Password alerts on spikes but does not yet automatically cut off spending.

Caveats

The current scope covers only three vendors: Anthropic, Cursor, and OpenAI. More vendors may be added based on demand, but no timeline is set. The product alerts but does not enforce; automatic spend limits are "actively evaluating" according to Henry. Organizations that need enforcement today will need to complement this with their own controls or vendor-native tools.

Henry noted that visibility must come first: "You can't enforce what you can't see." For now, AI cost management is best seen as a decision-support system for budget allocation, not a fully automated governance tool.