Billing

A seat is a person's account in the organization (a membership a person was given; an operator's automatic one is not counted, TENANT-ADMIN-COUNTS-PEOPLE) or an agent registered for it that runs on Tonoman Cloud's compute. An agent on the customer's own compute (a worker pool, POOL-SEES-ONLY-ITS-OWN) is not a seat, however many there are.

The first agents and the first people are free, counted apart: 1 always-on agent and 3 people unless the platform says otherwise. Beyond them every seat is paid, at the seat price — $14 a month unless the platform says otherwise. A free person's seat is never spent on an agent, nor the other way.

e.g. 2 always-on agents, 5 people → 1 + 2 = 3 paid seats, $42 a month; 9 agents on the customer's own compute → still 0 for those.

The free agents, the free people, the seat price, each add-on's price and the transcription day's limit are the platform's settings, changed by an operator on the Hub's platform settings, and read from there by billing and by the public pricing page alike — the price on the site is the price charged. A new price applies to new subscriptions; an existing one keeps the price it was taken at until changed in Stripe.

Every agent answers on its tenant's own model login — Claude or Codex, the customer's subscription — so nothing is charged twice. The platform supplies inference only as an add-on (transcription today).

Transcription by the platform is an add-on, $19.97 a month unless the platform says otherwise: unlimited, up to 24 hours of audio a day for the tenant. Without it, or past the day's limit once enforced, a recording is not transcribed by the platform and the person is told why; a tenant may bring its own transcriber instead.

A hosted website the agents edit is an add-on, $19.97 a month unless the platform says otherwise, with unlimited edits.

Limits and add-ons are metered from the start but only enforced once an operator turns enforcement on in the platform settings, so no tenant using transcription today loses it the day billing arrives.

An owner or admin subscribes on the tenant's Billing page: seats, and any add-on, through Stripe's own checkout — the Hub never sees a card. Card and invoices are managed in Stripe's billing portal, opened from the same page.

When a person joins or leaves the organization, or an agent moves onto or off Tonoman Cloud's compute, the paid seats on the subscription follow, prorated by Stripe.

Cancelling the plan or an add-on keeps it working to the end of the month already paid for, then ends it; the Billing page says until when. Cancelling again before then is the same; resuming before then undoes it.

e.g. transcription cancelled on Oct 12, paid to Oct 31 → recordings are transcribed until Oct 31, then not.

What a tenant has is what Stripe says: a subscription's state, its end and what is on it arrive by Stripe's signed webhook and are kept; one not signed with the platform's secret changes nothing.

The Billing page shows the plan with the free seats and those in use, the paid seats and what they cost, each add-on (on, ending on a date, or off) and this month's usage of each metered thing.

Anything metered is recorded as a usage event: which meter, how much, when, for which tenant — and, when known, which agent, which person and what it was for — once, by a key the reporter gives, so a retry is not counted twice. Meters are rows, not code: transcription seconds, website edits, website visits; more as the platform offers more (other kinds of inference).

Each event adds to its tenant's total for that meter and that day, in the same write, so a limit is checked against one row and the Billing page reads a month in a handful.

Each recording the platform transcribes is reported in seconds of audio; before transcribing, the worker asks whether the tenant may (BILL-ADDON-TRANSCRIPTION), and a refusal is said, never a silent skip.

Each change the website skill makes to a site is reported as one edit.