← Go back

Guide // MandateGuard

How do you control AI agent subscription spending?

By the Ingenious AI team · Published 2026-11-14 · Reviewed 2026-11-14

▸ Run the free live demo See pricing

Free covers 1 agent and 1 policy with the full authorize flow, signed receipts and the approval inbox — no card required to start.

Short answer

Control agent subscription spending at the commitment, not the charge: require approval for every new subscription start regardless of size, run duplicate-commitment detection so the same vendor-and-amount commitment cannot be taken twice inside your window without a human seeing the original receipt, and keep a renewal tracker seeded from the receipt chain. The subscription register an agent creates is otherwise invisible until statements arrive; with a mandate, every start, upgrade and duplicate attempt is a signed decision. A quarterly zombie review — cancelling commitments whose purpose has ended — routinely recovers a meaningful share of the fleet's spend.

What is a subscription commitment, in mandate terms?

Subscription spending control means governing the recurring commitments an agent creates: each start, upgrade and renewal the agent initiates is an authorize decision against its mandate, with duplicate-commitment detection (Pro and Team) watching for the same vendor-and-amount commitment being taken on twice inside your window, and the receipt chain preserving every commitment's origin — which agent, which task, which approval.

Subscriptions are commitments, not purchases

A purchase ends; a subscription repeats. That single property changes the control problem: the risk is not the first 49 dollars but the unnoticed eleventh renewal, the overlap bought by a second workflow, the trial that converted while nobody was watching. Agents are prolific subscription starters because starting is how they solve problems — a tool for this task, a tier for that limit. Without a mandate, a workspace accumulates commitments the way browsers accumulate tabs. With one, every start is a decision with a receipt, and the collection of receipts becomes the subscription register the business never had. The control goal is not to prevent subscriptions; it is to make every one of them chosen, visible and owned.

Gate the start, not just the size

The decisive moment is the start, because starts are where novelty lives. Amount thresholds help — many subscriptions are priced to slip under casual review — but the stronger pattern is novelty-based: first purchase from any vendor requires approval, whatever its size, so every new recurring relationship begins with a human's yes. Express it as a written condition in the approver runbook for standing policies, or on the envelope for task-scoped agents. Once started, a subscription's renewals are the expected shape of spend; the approval system's attention is better spent on the starts, the upgrades and the duplicates than on re-judging the same 49 dollars monthly until approvers stop seeing it.

Duplicate detection: the subscription-specific control

Duplicates are the subscription disease in its purest form: the same commitment taken twice — two workflows subscribing independently, a retry re-subscribing after a timeout, a trial conversion landing beside a direct purchase. Per-request checks cannot see it; the pattern lives in history. MandateGuard's duplicate-commitment detection (Pro and Team) reads the workspace ledger for the same vendor and amount inside your window and escalates the second authorisation to a human with the original receipt attached. The reviewer's question is simple: is the first commitment still in force and covering this need? Most escalations resolve as saves. Track the save count; it is the most persuasive number in the whole control programme when budgets are reviewed.

Make renewals visible as a class

Renewals should be reviewable as a list, not discovered as line items. The receipt chain gives you the raw material: filter decisions by vendor recurrence and task reference, and you have the renewal calendar the agent has created. Keep a lightweight tracker alongside — subscription, vendor, amount, renewal date, owning task, business purpose — seeded from receipts at the monthly review. Two disciplines keep it honest: every new start is added the week it is approved (the approval is the trigger), and every tracker entry must point at receipts. A tracker that disagrees with the chain is a finding, not a nuisance: one of them is describing subscriptions the other cannot see, and the unseen ones are the risk.

The zombie review

Quarterly, read the subscription list against reality: which of these does a live task still use? Zombies have tells in the receipts — task references naming ended projects, purposes nobody can explain, tools whose category the business replaced. Cancel through the vendor (MandateGuard governs authority, not the vendor's cancellation flow), then verify in the following cycle's receipts that the charges stop; a cancellation that does not stop charges is a vendor issue the receipts now evidence precisely. Report the recovered monthly figure to whoever funds the agent programme. Zombie reviews routinely recover a double-digit percentage of an unsupervised fleet's spend, and they convert sceptics faster than any policy document.

Upgrades, seats and other quiet expansions

Subscriptions also grow without new starts: tier upgrades, seat additions, usage overages converting to paid tiers. Each expansion the agent initiates is an authorize call, so the mandate sees them — upgrades usually breach the amount pattern of the subscription's history, which is why approvers should treat a familiar vendor at an unfamiliar amount as a novelty event worth a question. Vendor trust helps here: the per-vendor view shows totals and decision patterns accumulating, so a subscription quietly doubling its monthly draw is visible as a trend rather than a surprise. The governing principle is constant: recurring money deserves recurring scrutiny, and the receipts make that scrutiny a fifteen-minute habit instead of a forensic project.

Five actions to take now

  1. Register every agent-started subscription with its renewal date in your own tracker
  2. Set approve-over low enough that new subscriptions always pause for a human
  3. Turn on duplicate detection and act on its escalations the same week
  4. Review the receipts for renewals monthly — zombie subscriptions announce themselves there
  5. Cancel through the vendor, then watch the next cycle's receipts to confirm the charges stop

Worked example: eleven subscriptions, five cancellations, 1,872 dollars a year

An audit of one workspace's receipts finds the agent holding eleven subscriptions: four load-bearing tools, three overlapping analytics products bought by different workflows across two months (49, 49 and 39 dollars monthly), two free-trial conversions nobody ordered explicitly (25 and 15 dollars), a duplicate dataset licence already flagged once by duplicate detection and approved in error, and one zombie — a design tool unused since its project ended, renewing at 30 dollars.

The cleanup cancels five, saving 156 dollars a month — 1,872 dollars a year — from a workspace whose total agent spend was under 900 dollars a month. Every fact in the audit came from the receipt chain: no statement archaeology, no vendor interrogation. The standing fix is procedural: new subscriptions always need approval, and the renewal review joins the monthly policy review.

Frequently asked questions

Does MandateGuard stop a vendor from charging a renewal directly?

MandateGuard governs spends the agent initiates through authorize. A vendor charging a stored card directly is outside the agent's flow — which is why agent-started subscriptions should be structured so renewals pass through the agent's checked path, and why reconciling statements still matters.

How does duplicate detection treat renewals?

It watches for the same vendor and amount authorised again inside your window. A renewal at the expected interval is a human decision at escalation — the reviewer sees the original receipt and judges.

Can I require approval only for new subscriptions, not renewals?

Use the threshold for amounts and approver practice for novelty: first purchase from a vendor is a written condition in the runbook or on the task's envelope.

What is a zombie subscription?

A recurring commitment whose purpose ended — project closed, tool replaced, workflow deleted — that keeps renewing because nobody owns its cancellation. Receipt reviews surface them by task reference.

Which plan do I need for duplicate detection?

Pro or Team. The free plan's receipts still make a manual subscription audit possible, as the worked example's method shows.

Keep reading

Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides