Create Accountor Login
Docs

Your AI Agent and Subscriptions

Part of the MountDev Ops Subscriptions documentation. Updated November 19, 2026

MountDev Ops Subscriptions documentation | Updated November 19, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

What It Is

Your own AI agent, connected to your workspace, can set up your catalog and your clients' subscriptions with nine tools that know what a product, a subscription, and an item mean. They are made for the work: you can ask your agent to "add a product called Standard Care at $49 a month, then subscribe Acme Test Co to it with two items", and it does the safe version of each step.

The tools follow the same rules on every account. They check what the person who connected the agent may do, the same as the screens do, and they never do more than that person could. Every change is marked AI agent in the Activity Log.

Who Can Use It

Owners and admins at first. Two permissions, held by people and given through a role or a permission group, decide it:

  • Add and change products and their prices (subscriptions.products_manage) for the product tools.
  • Add and change clients' subscriptions and their items (subscriptions.subscriptions_manage) for the subscription, item, and check tools.

An agent never holds either on its own. It has them only as the person who approved its connection, and each tool is its own permission on the connection, so you can give an agent only the ones it needs (Settings, Connections).

The Rules Every Tool Follows

  • New things start off. A product an agent adds is saved inactive. A subscription an agent adds is saved Paused. An item added to a subscription that is not Active bills nothing.
  • Turning on, and anything that changes what a client pays, waits for your yes. The request appears on the Approvals card (and in Needs You Today) with the exact before and after in dollars for each field that changes, such as "Price | $39.00 | $49.00". Your yes covers exactly what the card showed. If the record is changed after the card was made, the yes is cancelled and the agent has to ask again.
  • An agent may pause a subscription, but never makes one Active or Cancelled. Pausing only lowers what is billed.
  • Nothing charges and nothing emails a client. No tool creates a charge, a payment, an invoice, or a message to a client. Only Invoices charges. The monthly run, Billing Active, adding services from a proposal, and ending a line stay with people.
  • Nothing is deleted. There is no tool that deletes a product, a subscription, or an item. A product is turned off, and a subscription is paused or cancelled by a person.
  • Repeating a save is safe. Every save tool takes an optional ref. A second call with the same ref for the same tool returns the first record and changes nothing, so an agent that tries again after a timeout never makes two.

The Tools

  • List products (subscriptions.products.list, MCP tool products_list): name, kind, billing interval, SKU, category, unit, whether it is active, and the price only if the person may see prices. Filter by name, category, or active. One page of up to 50.
  • Save a product (subscriptions.products.save, product_save): add a product (saved inactive) or change one by its id. Changing the price, billing interval, or kind of an active product waits for your yes. Changing an inactive product saves at once.
  • Turn a product on or off (subscriptions.products.enable, product_enable): turns a product off at once. Asking to turn it on waits for your yes. The answer says waiting_for_approval with an approval_id and a review_url, and the agent checks it with mountdev_check_approval.
  • List subscriptions (subscriptions.subscriptions.list, subscriptions_list): client, status, billing interval, next bill date, bill-to, and the number of items. Filter by client company and status. One page of up to 50.
  • Save a subscription (subscriptions.subscriptions.save, subscription_save): add a subscription for a client company (saved Paused), or change its name, billing interval, bill-to, dates, or notes by its id. It never sets the status. A subscription's company cannot be changed. Changing the interval, bill-to, or dates of an Active subscription waits for your yes. A name or notes change saves at once.
  • Change a subscription's status (subscriptions.subscriptions.state, subscription_state): pauses at once. Asking for Active or Cancelled waits for your yes, and the card shows the client, the items, and what the next monthly run would bill (only to a person who may see prices). Asking to bring a Cancelled subscription back, even to Paused, waits too.
  • List a subscription's items (subscriptions.items.list, subscription_items_list): description, product, website, quantity, unit price (only if the person may see prices), discount, dates, and service state. One page of up to 50.
  • Save an item (subscriptions.items.save, subscription_item_save): add an item to a subscription or change one by its id. On a subscription that is not Active it saves at once and bills nothing. On an Active one, a new item, or a change to quantity, unit price, discount, product, or dates, waits for your yes. A change to the description, details, or website saves at once. An item cannot be moved to another subscription.
  • Check a save (subscriptions.tools.check, subscription_tools_check): says what a save would do without saving it: which fields change, whether it would wait for a person, and why. It changes and sends nothing.

Amounts are dollars and cents as text, such as 49.00. A product's price, interval, and kind are checked, and a bad value gets a plain message that names the field and never the record's other values.

What a Person Sees and Does

When something waits, the agent gives you a link to the review. Open it in the workspace, read the before and after, and say yes or no. Only a person who holds the permission above can see or answer the card. An agent, an API key, or an assistant can never answer it. A card that is not answered expires after 24 hours.

After you say yes to turning a product on or making a subscription Active, nothing is billed yet. The next monthly run, which a person starts, includes the subscription only if Billing Active is on for that client, as before (The Monthly Run).

The Generic Record Tools Are Closed for These

An AI agent can still read products, subscriptions, and items with the generic record tools, but it cannot add, change, delete, or give away a record in them that way. The answer names the tool to use instead. The same is true for Invoices' invoices, invoice lines, payments, and billing accounts: an agent can read them, and billing actions are done by a person or through Invoices' own actions. This is a setting a module declares, the same for every app and every account. People, automations, and workflows are not affected.

What It Stores

One small table, subscriptions_tool_keys: for each save that used a ref, its tool, the ref, and the record it made. It is in Export Everything as Typed Tool Refs. The tools write products, subscriptions, and items as ordinary records, so history, search, events, and permissions work as they do for a person's change.

Not Included

Charging, refunding, invoicing, or emailing a client by any tool; running the monthly invoices; Billing Active; adding services from a proposal; ending a line; every delete; and API keys' reach into these records, which has its own review.

Ask Us Anything

We’d love to hear from you!