Credits and billing

Anything that costs GreenMind money each time it is used, such as AI, automated posting or processing media, is paid for in credits, bought ahead. One credit is one US cent. Editing, collaboration, history, comments, exports and the API are free. An org's credits are on the Billing tab of its page on your GreenMind account, and every product the org works in spends from them. What costs credits in Marketing, and how a price is shown before you spend, is in Marketing's Credits.

Anybody who may see the org's usage sees its Billing tab. Only the org's admins buy credits or change the budget and the limits.

The balance

The top of the tab shows what the org can spend now, credits set aside for projects (which only those projects can spend), and credits set aside for work still running. Credits granted to one project are spent by it before the org's own, and by nothing else.

Buying credits

Credits are sold in packs, each showing how many credits it buys and its price. Stripe sells them through Link, which adds tax where it applies and emails the receipt; card statements show LINK.COM. Credits appear on the tab as soon as Stripe confirms the payment. Bought credits never expire; credits GreenMind grants may.

Low credits and top-ups

Switch on Tell the admins when credits are low, and set:

• Warning threshold (credits): when the org's own credits fall below it, the admins are told on the Billing tab and in their GreenMind inbox.
• Top up by (USD): what the link in that notice buys, in one tap through Stripe Checkout.
• Budget a month (USD): top-ups never buy more than this in a calendar month. Packs bought by hand are not counted.

The admins are also told at 80% and at 100% of the budget, and the tab shows how much of this month's budget top-ups have used. Credits are never bought by themselves: a top-up is always somebody pressing the link.

Spending limits

Monthly limits inside the org, so one project or one feature cannot spend everything: a limit on a project, on a feature, or on a feature in one project. A feature's limit covers the features under it, so a limit on ai covers ai.text and ai.image. Work still running counts against a limit as it does against the balance. Each limit shows what has been used of it this month.

Something that would pass a limit is refused, and says so; an admin can raise the limit here.

The ledger

Every change to the org's credits, newest first: purchases, grants and spending, each with what it was for and the balance after it.