Plans and allowances
What each Mirra plan includes — screens, household members and assistant credits — how credits are metered, and what happens when you reach a limit.
Screens, household members and assistant credits all come from your plan. The scheduler and the REST API need Pro or above. Digital menu boards need one of the business plans, whatever else you are paying for.
What a plan decides
A plan sets three numbers and unlocks a small number of features. The numbers are how many screens you can pair, how many people you can add to Household, and how many assistant credits you get each calendar month.
All three are checked at the moment you act — when you pair a screen, when you add a person, when a screen starts an assistant turn — rather than applied retrospectively. That matters if you ever move down a plan. Nothing you already have is deleted, hidden or switched off. A household that drops from eight screens to three keeps all eight running and finds it cannot pair a ninth.
Sign-ins are not counted by any of this. The accounts that can log in to the portal are capped at 50 regardless of plan, and are covered in Sign-ins and roles.
The home plans
These are the plans a household buys. Every price is monthly, in pounds.
Plans are rows in a database, not constants in the code. An operator can change a price or a limit on any of them from the admin console, and a self-hosted install can carry a different ladder entirely. The Plan and usage page in your own portal, not this article, is the authority on what you are paying for.
The business plans
Signage plans are priced per estate rather than per household, because a retail chain buys screens and a family buys a mirror. They are kept as separate plans rather than a relabelling of the home ones, so the two ladders can be priced and grandfathered independently of each other.
Digital menu boards are the one feature decided by which ladder you are on rather than how far up it you have climbed. A household on the highest home plan does not reach menus and is not meant to — a kitchen wall has no use for a menu board. Every commercial plan reaches them.
Features above the numbers
Two areas of Mirra are gated by position on the ladder rather than by a count.
The scheduler — scene changes on a timetable — and the REST API with its webhooks both need Pro. The business plans sort above Pro, so all three of them reach the scheduler and the API as well.
Individual widgets carry their own minimum plan on top of that; the widget catalogue says which. Everything else follows the three numbers.
How assistant credits are metered
A credit is one token — one unit of text going into the model or coming back out. Credits are sold in tokens because that is the number you can reason about: a spoken question and its answer come to roughly 700 tokens, so 750,000 credits is roughly a thousand conversations a month rather than an abstraction.
Speech is deliberately outside the count. The seconds of audio transcribed and the characters synthesised for the spoken reply are both recorded against your account, and neither is deducted from your allowance. Folding them in later would quietly shrink every allowance already sold.
A web search made by the assistant costs 3,000 credits. That is what a search costs, converted at the model's input price and rounded up, rather than a figure chosen to feel expensive. Searches are stored as a count rather than converted to credits when they happen, so a change in the search price reprices the whole month rather than only the rest of it.
Reading the Plan and usage page
Three meters run across the top of the page: screens used against screens allowed, household members against members allowed, and assistant credits used this month against the allowance. Each bar turns red at ninety per cent.
Under the credits meter is an estimate — "About N more conversations this month" — worked out at 700 credits a conversation. Treat it as a working figure rather than a promise. A long answer with a web search in it costs several times that.
Open the account menu
Your name, at the top right of any portal page.
Choose Plan & usage
The page opens at /billing.
Read the three meters
Screens, household members, and assistant credits used this month.
The credit month is a calendar month and the meter resets on the 1st. Nothing carries over.
What happens when you reach a limit
- Screens — pairing is refused with "Your plan covers N screens. Upgrade to pair another." Everything already paired carries on as normal.
- Household members — adding is refused with "Your plan covers N household members. Upgrade to add more."
- Assistant credits — the relay asks before it reaches for a model, so a household with nothing left is told "You've used this month's assistant allowance" instead of getting a broken turn. The screen carries on showing everything else.
- Web search — refused separately once fewer than 3,000 credits remain. A search is a call to a third party and cannot be un-billed afterwards, so an exhausted household must not be able to make one.
- A plan with a zero credit allowance switches the assistant off outright: "The assistant isn't included on your plan."
- A suspended account cannot use the assistant, and cannot sign in to the portal either.
Bonus credits
An operator can add bonus credits to an account. They sit on top of the plan's monthly figure and show up in the allowance on the Plan and usage page, and they do not erase any usage already recorded.
They are not a one-off pot that drains away. The number is added to the allowance every month until somebody changes it.
There is no way to buy credits from inside Mirra. If you are running out every month, a larger plan is the answer.
Related
- BillingHow to subscribe, change plan, find your invoices and cancel — and what Mirra does on an install where payments were never configured.
- The assistant: how a conversation worksHow you summon Mirra, what happens between hearing you and answering you, which tools it can reach, where the transcript goes, and what a conversation costs against your monthly allowance.
- Letting the assistant look things upHow to switch web search on for your assistant, what a search costs, and why a conversation that reads the web can no longer change anything in your home.
- Menu boardsHow to build a menu in Mirra — sections, dishes, prices and photographs — put it on a screen through the menu board widget, and give kitchen staff a sign-in that reaches nothing else.
- The schedulerSchedule rules say which scene a screen shows from a given time on given days, and the Scheduler draws every screen's day as a timeline you can drag scenes onto.
- The REST API and your keysHow to create an API key, what a single key is allowed to reach, and every endpoint the public v1 API exposes.
- Pairing a screenHow a display joins your household: the six-character code it shows, what to type into Mirra, what pairing creates, and what happens when you unpair.
- People and presenceHow to add a household member, enrol their face on a screen, and understand what Mirra stores about them and where recognition actually happens.