Billing

Billing is per workspace. The plan a workspace is on decides eight allowances and four permissions, and everything metered in Tempio is metered against the workspace rather than against the person who happened to press the button.

What a plan includes

Scale is priced on ad spend rather than on a sticker: the app quotes the allowances above and answers an upgrade with an address to write to, which is why no figure for it appears here or in the plan dialog.

The plan dialog on Billing is the source for all of it — the allowances above and what each plan costs, monthly or yearly as the switch is set, read from the same catalogue the checkout charges from. The numbers are repeated here to be read, not to be relied on over the app.

Each row is enforced where it is spent, not at the till: connecting an account checks the connection allowance before the platform's sign-in starts, minting a key checks the key allowance, inviting somebody checks seats, creating a workspace checks workspaces, and watching or saving an ad in the ad library checks its own row. The refusal names the limit and says upgrading is the remedy — a different name or a second attempt is not going to fix it, so nothing retries into the same wall.

Two details worth knowing. A revoked MCP key grants nothing, so it costs no allowance and never blocks a replacement being minted. A pending invitation does hold a seat, because the alternative is a queue of acceptances that cannot all fit.

Two of those rows are worth reading twice. Editable guardrails is not a looser gate on a bigger plan: the mechanism is identical on every plan, and the three caps a budget change is held to are resolved the same way whatever you pay. What the permission buys is the right to put a number of your own in front of the derived one — for the whole workspace, for one connection, or for a single ad account, higher or lower than the number Tempio worked out — written by an owner or an admin, audited, and stamped onto every draft it decided, so the draft says which cap it was checked against and who set it. Two things stay ours on every plan and no override moves them: the running twenty-four-hour total of budget increases on a connection, and the kill switch. Client sign-off is the signed link that lets somebody who holds no seat approve one batch and nothing else; it satisfies a client stage on an approval chain.

What a metered message is

One message you send to the agent is one unit. Not one tool call, not one model reply, not one retry inside a turn — one thing you typed and sent. A question that makes the agent read ten campaigns costs the same as one that makes it read none.

Nothing else counts against this pool. Syncs, drafts, approvals, plans, media uploads and every call your own AI makes over MCP are not counted, and neither is a generated still, which has a pool of its own (below). The message pool is for the conversation, because the conversation is the part that runs a model.

What a creative generation is

One scene an image model draws for a generated still is one generation: a Create, a Clone or an Edit. A batch of ten is ten. Resizing a still and changing its copy are drawn by Tempio's own renderer and cost nothing, and so does the automatic retry when a scene comes back with text on it. A generation that fails is refunded, so a batch that lands eight of ten counts eight.

The allowance resets each billing period like the message allowance, and it has no packs: agent-message packs are never spent on generations. A workspace that adds its own OpenAI or Google image key under Settings → Integrations generates on that key and outside the allowance; its generations are still recorded and shown on that page.

Allowance, then packs

A workspace can hold two kinds of message credit, and they are spent in a fixed order.

1. The monthly allowance. It comes with the plan and it resets at the start of each billing period. Unused messages do not roll over.
2. Prepaid packs. Bought when you want more, they roll over and are the workspace's until they are used. The oldest pack is spent first, so a pack never sits behind a newer one.

Spending the allowance first is what keeps a pack from being burned in a month whose allowance was never finished.

Each purchase adds its messages once and only once: a replayed payment notification cannot grant the same pack twice.

The daily brake

There is also a soft daily cap on agent messages. It is an abuse brake and not a billing construct: it denies the message without spending anything from either pool, so nothing is lost when it bites. It exists so a runaway loop costs a day rather than a plan.

When either limit stops a message you see one line — you have reached your agent message limit — and the usage card on the dashboard shows which pool is empty.

Reading your usage

The usage card on Billing states the plan, the allowance, how much of it has gone this period, the prepaid balance, and the period the allowance is measured over. It reads the same resolver the gate spends against, so what the card says and what the chat does cannot disagree.

Changing plan

Upgrading and downgrading are both in the plan dialog on Billing. An upgrade's new allowances apply to the workspace immediately; entitlements are resolved per request rather than cached, so a seat or a connection that was refused a minute ago is available as soon as the subscription is active.

A downgrade is worth one thought: allowances are checked when something is spent, not swept afterwards. A workspace that drops to a plan with fewer connections keeps the connections it already has and cannot add another until it is back under the new number.

Who can do what

Changing the plan is an owner's or an admin's, and a member's Billing page shows the plan with no button to change it. Any member can buy a pack, because the pool is shared. Anyone in the workspace spends the pool by using the agent, and everyone can see the usage card — a shared allowance nobody can see is a shared allowance that runs out unexpectedly.

Comped workspaces

Some workspaces are on a founder plan, which is granted rather than sold and carries no message limit. Usage is still recorded on those: a comped workspace is exactly the one where knowing what is being used matters.