Cap the Blackbox agent. Keep the provider key.
A Blackbox chat session, Blackbox autocomplete job, or Blackbox agentic coding run can keep calling a standing provider secret after the planned run has finished. Issue a Till key for that session with a required request ceiling so remaining capacity stays readable and the agent can stop.
Isolate the Blackbox traffic, not the provider account.
-
01
Issue a disposable Till key for the Blackbox-agent job
Set the request ceiling from the planned session, retries, and tool loops, then add optional token, estimated-spend, expiry, and IP bounds when the agent needs a tighter envelope.
-
02
The provider credential stays behind Till
The Blackbox job uses a Till key, not an unconstrained provider secret in the editor or chat session. When the job is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not Blackbox, a coding agent, or a secret scanner
Till does not write code, complete snippets, or replace Blackbox. 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 Blackbox-agent 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 coding agent, 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 run. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.