# Billing

One flat monthly subscription per tier. No per-credit charges, no top-up
lines, no surprises indexed to estimate size. Pricing is deliberately
thin: a small line item next to your AI bill, with at least half of
subscription revenue to date spent on the certificates themselves.

> Checkout is not yet open; these are the planned launch tiers and they may
> change before launch.

## Tiers

| Tier | Price | Billable tokens / month | Retirements |
|---|---|---|---|
| Free | $0 | 10M | Estimates only |
| Personal | $12/mo | 25M | Bundled, accrued at P90 |
| Team | $55/mo | 100M | Bundled, accrued at P90 |
| Business | $435/mo | 1B | Bundled, accrued at P90 |
| Enterprise | Custom | Above 1B | Negotiated volume, named projects |

## Billable tokens

Tier caps count billable tokens, not raw tokens:

```
billable = fresh input + output + 10% x cached input
```

Cache reads cost providers about a tenth of the compute, and counting them
like fresh tokens would overcharge exactly the teams that engineered their
usage well. The 10 percent rate is a fixed billing rule, deliberately
separate from the estimation methodology: revising a methodology
coefficient can change an estimate, never your bill.

**Cache-heavy example**: 4,000M tokens tracked, 93 percent cache reads.
Billable = 280M fresh and output + 372M (10 percent of 3,720M cached) =
652M, which fits the Business tier despite four billion raw tokens.

**Reasoning-heavy example**: 60M input + 30M output (of which 25M are
reasoning tokens), no caching. Billable = 90M, which fits the Team tier.
Reasoning tokens are a reported subset of output tokens, so they are
already inside the output count and are never added again; they matter to
the footprint estimate, not to the bill.

## Why tokens, never footprint

Your bill depends only on token counts you can audit from your provider's
own reporting. No coefficient in the methodology can influence revenue, so
the estimates stay honest and so does the price.

## The certificate-share floor

At least 50 percent of your subscription revenue to date must have been
spent acquiring environmental certificates: retired for your benefit, or
purchased into retirement buffer inventory when your usage needed less
than the floor. The share is measured cumulatively on a cash basis at
actual supplier cost (never a price table), and any shortfall is trued up
with an additional purchase at each monthly close, rounding up to whole
units so the floor is met rather than approached. The cumulative achieved
share is recorded at every close and printed on your certificate. It is a
spending commitment on the subscription price, not a representation about
footprint coverage, which is governed by the estimate basis stated on the
certificate.

## At the cap

Estimation continues past the cap; nothing is gated or interrupted.
Retirements accrue up to the cap, and sustained billable usage above it
moves you to the next tier at the following billing period, with notice.
The certificate always states the token volume the period's retirements
were accrued against.

## Managing the subscription

The Manage billing button in the console opens the Stripe customer portal:
card changes, invoice history, and cancellation. If service lapses, your
AI tools are unaffected (the platform never touches your traffic); the
ledger simply stops accruing retirements, and your history and
certificates remain accessible.

## Annual billing

Annual billing with two months free is available on Team and Business;
write to info@tahosasystems.com.