Cap the call. Keep the provider key.
A phone, IVR, or realtime voice agent can loop speech-to-text, generation, and TTS against a standing provider secret. Issue a Till key for that session with a required request ceiling so remaining capacity stays readable and the call can stop.
Isolate the voice traffic, not the provider account.
-
01
Issue a disposable Till key for the session
Set the request ceiling from the expected turns, then add optional token, estimated-spend, expiry, and IP bounds when the runtime needs a tighter envelope.
-
02
The provider credential stays behind Till
The voice runtime uses a Till key, not an unconstrained provider secret in the telephony stack. When the campaign is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a phone system or speech engine
Till does not place calls, transcribe audio, or host SIP. 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 voice session 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 telephony platform, 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 session. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.