Cap the summary. Keep the provider key.
A document-summarization or recap job can keep calling a standing provider secret after the batch is done. Issue a Till key for that job with a required request ceiling so remaining capacity stays readable and the summarizer can stop.
Isolate the summary traffic, not the provider account.
-
01
Issue a disposable Till key for the job
Set the request ceiling from expected documents and retries, then add optional token, estimated-spend, expiry, and IP bounds when the summarizer needs a tighter envelope.
-
02
The provider credential stays behind Till
The summarization job uses a Till key, not an unconstrained provider secret in the recap process. When the corpus is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a summarizer or document pipeline
Till does not summarize documents, store corpora, or replace your recap pipeline. 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 summarization 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 document store, 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 batch. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.