Cap the pipeline. Keep the provider key.
A CI job can call models on every push or pull request against a standing provider secret. Issue a Till key for that run with a required request ceiling so remaining capacity stays readable and the job can stop.
Isolate the pipeline traffic, not the provider account.
-
01
Issue a disposable Till key for the job
Set the request ceiling from the expected model calls, then add optional token, estimated-spend, expiry, and IP bounds when the runner needs a tighter envelope.
-
02
The provider credential stays behind Till
The CI job uses a Till key, not an unconstrained provider secret in the runner. When the pipeline is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a CI runner or Actions replacement
Till does not host GitHub Actions, GitLab CI, or your build. 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 CI job 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 CI 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 job. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.