Cap the playground. Keep the provider key.
An internal chat playground can share one standing provider secret across every prompt, retry, and model switch. Issue a Till key for that UI with a required request ceiling so remaining capacity stays readable and the playground can stop.
Isolate the trial traffic, not the provider account.
-
01
Issue a disposable Till key for the playground
Set the request ceiling from expected team trials, then add optional token, estimated-spend, expiry, and IP bounds when the UI needs a tighter envelope.
-
02
The provider credential stays behind Till
The playground uses a Till key, not an unconstrained provider secret in the app. When the UI is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a playground host or chat UI
Till does not host your playground, store prompts, or replace the frontend. It is a hosted control layer in front of 12 AI providers: a required request ceiling and optional token, spend, expiry, and IP controls.
-
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 playground 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, a chat host, 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.
Run the trials. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.