Admin

Every number is in credits (1 credit = 37,500 weighted, model-cost-scaled tokens) — hover any of them for the exact token count. Usage is summed per calendar month; credits left are unspent packs, which the free plan runs on entirely (its monthly budget is 0). An email shows up once that account has made a request.

Added credits never expire and are spent after the monthly plan budget, oldest pack first. Removing takes from the oldest unspent pack and stops at zero — it can't push a balance negative. Credits for an email that has never signed in are parked and land on that account's first request.

The weight is how many weighted tokens one raw token bills (cache reads bill at a tenth of it, cache writes at 1.25×), and 1 credit = 37,500 weighted tokens — so credits per 1k raw tokens = weight ÷ 37.5. Saving an override reprices new usage within a minute; leave the field blank and save to return to the built-in weight. Every served model is listed, including ones added without a built-in weight yet — those meter at the “fallback” flagship rate until you set a weight here (or one ships in code).

Buyers redeem these in the Stripe checkout’s “Add promotion code” box, which enforces the expiry date (end of that day, UTC) and the use cap at payment time. Adjusting a code replaces it on Stripe under the same name and re-arms it if it was revoked. Visitors arriving through an affiliate link already get the referral discount and don’t see the code box — Stripe never stacks the two.

“Stripe transfer” pays the affiliate’s connected account for real; “manual” only marks the commissions paid — send the money out-of-band first.