Separate the experiment. Cap the envelope.
A shared provider key mixes every trial into one counter. Issue a Till pass per project so remaining capacity is easier to read, the required request ceiling belongs to that experiment, and the key can end when the trial ends.
Bound the experiment, not the provider account.
-
01
One experiment, one operating envelope
Every Till key requires a request ceiling. Add optional token, estimated spend, expiry, and source IP controls when the trial needs a tighter bound.
-
02
Counters stay with the project
Separate credentials by team, project, or environment so remaining activations, tokens, and estimated spend are readable without mixing every experiment into one shared key.
-
03
End one trial
Revoke or let expiry stop that experiment without rotating every provider connection. The Till key is still a bearer secret; the difference is that it can end.
-
04
Pro is the plan for concurrent experiments
$59/month, 25 scoped keys, 25,000 monthly activations (plan limits). Provider inference is billed by the provider. Till charges a platform subscription.
Till is a hosted control layer for AI provider credentials. Connect provider accounts once. Each workload gets a disposable Till key with a required request ceiling and optional token, estimated-spend, expiry, and IP controls across 12 providers. Till is not a zero-knowledge vault, prompt firewall, secrets-manager replacement, compliance certification, 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 it enough. Not everything.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.