Cap the review. Keep the provider key.
A pull-request review, comment, or summary job can keep calling a standing provider secret after the diff is done. Issue a Till key for that review with a required request ceiling so remaining capacity stays readable and the bot can stop.
Isolate the review traffic, not the provider account.
-
01
Issue a disposable Till key for the review job
Set the request ceiling from expected diffs and comments, then add optional token, estimated-spend, expiry, and IP bounds when the bot needs a tighter envelope.
-
02
The provider credential stays behind Till
The review job uses a Till key, not an unconstrained provider secret in the bot process. When the reviewer is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a code-review or git host
Till does not comment on pull requests, host GitHub, or replace Copilot or your review bot. 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 review 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 code-review product, 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.
Finish the diff. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.