Split the budget. Cap each key.
A shared provider credential mixes every team into one counter. Issue a Till key per team or project so remaining activations and estimated spend stay readable, and that key can end without rotating every connection.
Bound the team, not the provider account.
-
01
Issue a Till key per team or project
Set the required request ceiling from that workload, then add optional token, estimated-spend, expiry, and IP bounds when the team needs a tighter envelope.
-
02
Counters stay with the key
Each scoped key has its own activations, tokens, and estimated spend. Remaining capacity is readable without mixing every team into one shared provider credential.
-
03
This is not a cost-allocation platform
Till enforces per-key limits. It does not pool a shared team wallet, replace provider invoices, or certify chargeback. Estimates may differ from provider billing.
-
04
Pro: $59/month, 25 scoped keys, 25,000 monthly activations
Those are plan limits. Public signup is closed; request Pro beta access. Provider inference is billed by the provider. Till charges a platform subscription.
Connect provider accounts once. Each team or project gets a disposable Till key with a required request ceiling and optional token, estimated-spend, expiry, and IP controls. Till is not a zero-knowledge vault, FinOps suite, or a replacement for provider billing or IAM.
These are plan limits, not usage claims.
Pro
Scale
Public anonymous signup is closed. New accounts are approved and provisioned manually. Existing customers can open the dashboard. Compare the full ledger on pricing.
Give the team a ceiling. Keep the credential.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.