Separate product logic from live billing state.
GitMir supplies how plans, permissions and limits work; your billing systems supply the current subscription and authorized actions.
How plans, permissions and limits are actually implemented lives in code, and that is what GitMir reads. The current subscription, the balance and the charge stay in your billing system. An agent can ask what a downgrade would reach and how risky it is before anything is touched, then act with your own billing tools.
Ask what the product calls the thing you mean — "plan", "entitlement", "seat".
Ask what a change to it would reach, in both directions, and how risky that is.
Ask whether the move you intend is allowed from the state your system reports.
Perform the billing action in your billing system.
No screen for this and no connector to a billing system — MCP only. GitMir does not read your Stripe, your invoices or your balances — the billing page in the workspace is your own GitMir subscription and nothing else — and it cannot tell you what a given customer is entitled to; it can only tell you how entitlement is built in the product. Every answer reflects the last build of the code, not what shipped an hour ago.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.