Cap the notebook. Keep the provider key.
A Jupyter, Colab, or shared research notebook can keep a standing provider secret after the session ends. Issue a Till key for that notebook with a required request ceiling so remaining capacity stays readable and the session can stop.
Isolate the notebook traffic, not the provider account.
-
01
Issue a disposable Till key for the notebook
Set the request ceiling from the session plan, then add optional token, estimated-spend, expiry, and IP bounds when the notebook needs a tighter envelope.
-
02
The provider credential stays behind Till
The notebook uses a Till key, not an unconstrained provider secret in a cell or environment. When the session is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a notebook host or secrets manager
Till does not run Jupyter, store notebooks, or replace your vault. 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 notebook session 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 notebook platform, 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 notebook. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.