Cap the SQL. Keep the provider key.
A text-to-SQL, query-rewrite, or schema-to-query batch can keep calling a standing provider secret after the statements are drafted. Issue a Till key for that job with a required request ceiling so remaining capacity stays readable and the worker can stop.
Isolate the SQL traffic, not the provider account.
-
01
Issue a disposable Till key for the SQL job
Set the request ceiling from expected schemas and retries, then add optional token, estimated-spend, expiry, and IP bounds when the generator needs a tighter envelope.
-
02
The provider credential stays behind Till
The SQL job uses a Till key, not an unconstrained provider secret in the worker process. When the job is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a SQL generator or database engine
Till does not write SQL, execute queries, or replace your warehouse 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 SQL 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 SQL generator, 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 queue. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.