Pricing

Tiers are priced on billable tokens per month, never on footprint. Cached input counts at a tenth, since cache reads skip most of the compute. Certificate retirements are bundled into every paid tier and accrue at the conservative end of the estimate range (P90) for every account. Pricing is deliberately thin: a small line item next to your AI bill, with at least half of every subscription spent on the certificates themselves.

Preview pricing. Checkout currently runs in Stripe TEST mode while supplier contracts and counsel review complete: no real card is charged, and accounts created now are preview accounts. Tiers may change before launch.

Free

$0

Up to 10M billable tokens / month

Estimates only. The reference implementation of the methodology, open to everyone.

  • ·Usage-phase footprint estimates with full 90 percent ranges
  • ·Metadata-only metering API
  • ·Public versioned methodology and changelog
  • ·Console dashboard
  • ·No certificate retirements
View the demo console

Personal

$12 / month

Up to 25M billable tokens / month

For individuals whose AI usage deserves a real record.

  • ·Everything in Free
  • ·Certificate retirements bundled to the token cap, accrued at P90
  • ·At least half of your subscription spent on certificates, disclosed each period
  • ·Water, carbon, and renewable energy certificates
  • ·Monthly certificates with project identities
  • ·Approved claim language schedule
Start now

Team

start here

$55 / month

Up to 100M billable tokens / month

Retirements bundled. One flat bill, no per-credit charges.

  • ·Everything in Free
  • ·Certificate retirements bundled to the token cap, accrued at P90
  • ·At least half of your subscription spent on certificates, disclosed each period
  • ·Water, carbon, and renewable energy certificates
  • ·Monthly four-section certificates with project identities
  • ·Approved claim language schedule
  • ·Email support
Start now

Business

$435 / month

Up to 1B billable tokens / month

For AI-native products with reporting obligations.

  • ·Everything in Team
  • ·Reporting exports (water restoration summary, CDP Water, ESRS E3 inputs)
  • ·Generated disclosure records (California AB 1305 support)
  • ·Multiple API keys and per-provider views
  • ·Priority support
Start now

Enterprise

Custom

Above 1B billable tokens / month

Negotiated volume, named projects, audit support.

  • ·Everything in Business
  • ·Named-beneficiary retirements where the supplier registry supports it
  • ·Named project selection and geographic preferences
  • ·Audit support and records access
  • ·DPA, procurement, and legal review support
  • ·Methodology review participation
Contact us

Billable tokens, explained

Modern AI workloads reuse the same context over and over, and providers serve those cache reads with about a tenth of the compute. Counting them like fresh tokens would overcharge exactly the teams that engineered their usage well, so tier caps count billable tokens:

billable = fresh input + output + reasoning + 10% × cached input

A worked example: a firm that looks huge on paper

Tokens tracked in a month4,000Mof which cache reads (93%)3,720M × 10% = 372M billablefresh input, output, reasoning (7%)280M billableBillable tokens652M → Business tier

Every count comes from your provider's own usage reporting, so your bill is auditable from numbers you can verify. The 10 percent cached rate is a fixed billing rule, kept deliberately separate from the estimation methodology: revising a methodology coefficient can change an estimate, never your bill. The footprint estimate itself also credits cache reads, at the methodology's own cached-input coefficient.

Why tokens, not footprint

Your bill depends only on tokens tracked, a number you report and can audit, never on estimated gallons, tonnes, or credit value. That separation is deliberate: no coefficient in our methodology can influence our revenue, so the estimates stay honest and so does the price. If a methodology revision changes an estimate, your subscription does not move.

Where your subscription goes

At least 50 percent of every subscription is spent acquiring verified certificates, enforced at every monthly close. If your usage needs less than the floor, the remainder buys additional water restoration certificates into the retirement buffer. The achieved share is computed at close and disclosed on each period's certificate, so the commitment is auditable, not aspirational.

Why retirements accrue at P90

Footprint estimates carry wide, honestly stated ranges. Bundled retirements accrue at the 90th percentile of that range rather than the midpoint, so the retired quantity plausibly meets or exceeds the estimate in nine cases out of ten. Certificates state this basis explicitly: retired against the 90th percentile of the estimate range, never presented as exact matching or as any neutrality status.

What happens at the token cap

Estimation continues past the cap; nothing is ever 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, and the credit value retired is shown on every certificate for transparency even though it is never billed separately.

Annual billing with two months free is available on Team and Business. All claims customers may make about retirements are governed by the approved language in the Terms of Service; footprint figures are modeled estimates with stated ranges per the methodology.

Next: see the ledger live

Open the console