Cap the job. Keep the credential.
A CI job, cron, or batch pipeline should not inherit a standing provider secret. Issue a Till pass with a required request ceiling so the automation can finish and then cannot keep going.
Bound the pipeline, not the provider account.
-
01
Issue a disposable Till key for the job
Set the request ceiling from the run plan, then add optional token, estimated-spend, expiry, and IP bounds when the pipeline needs a tighter envelope.
-
02
The provider credential stays behind Till
The automation uses a Till key, not an unconstrained provider secret in CI. When the job is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a secrets-manager replacement
Vaults store keys. They do not end them when the pipeline ends. Till is a hosted control layer in front of 12 AI providers, not a general vault, prompt firewall, or compliance certification.
-
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 automation 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 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 job. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.