buckette for token-maxxers
You pay for a capped AI allowance: a weekly limit, a five-hour window, a monthly budget shared by a team. The cap is not the problem. Running out on Wednesday is, and so is an agent that takes the share you kept for chat. buckette gives you a pacer: it holds the cost before each run, grows the hold when the run needs more, and settles what the run really used.
One allowance, split by use
- One bucket for the allowance, one child per use. Split a child bucket for chat, one for each agent, one for each task, and give each child its own key, scoped to that child. An agent holding the key of its child cannot spend the others’ share.
- A floor under the slice you must not lose. Consume classes put a floor under part of the balance: a request of a lower class succeeds only if what it leaves stays at or above the floor. Your agents can use the allowance up to the floor, and the last of it stays for chat.
- Leftovers flow back. Reclaim a child when its work ends, and what it did not use returns to the allowance.
A pacer, not a promise
An agent that promises to watch its own usage can forget. The pacer keeps the meter outside the agent:
- Hold before the run. Reserve what the run is expected to use. If there is no room, the run is told before it starts, not halfway through, and buckette can estimate when there will be room again, from the allowance’s refill schedule.
- Keep and grow the hold while it runs. Refresh the hold so it does not lapse, and grow it when the run needs more than it held. A grow is checked like a new reservation, and it is all or nothing.
- Settle what was used. Commit the actual amount when the run ends. The rest of the hold goes back to the allowance; a run that used nothing commits zero and gives the whole hold back.
See the week coming
- Pacing within the period. buckette returns what was consumed in each slice of the open period, per class, with the time of the next reset. Read it against the previous period to see whether this week is running ahead of the last.
- Where it went. Put a session, a model or a project in each consumption’s metadata, and buckette breaks the consumption down by it.
- A warning before a reset. When a scheduled refill is about to throw away an unspent balance, a webhook says so ahead of time, so you can spend it rather than lose it.
- Low-balance warnings. Webhooks fire as a balance crosses the levels you set.
What buckette does not do
buckette meters what you report to it. It cannot see a provider’s own counter, and it does not change what a provider charges you. Where you can count the use (a wrapper around your agent, a usage report, a proxy), buckette keeps the account and holds each use to its share.
Try it
Create a tenant in the Console and follow
Getting started. The reservations help
topic on your tenant’s address describes the hold, the grow and the commit.