Share access. Not the provider key.
A contractor needs enough AI access to finish the project. They do not need the standing provider credential that outlives the contract.
Hand over a disposable key, not the account.
-
01
Issue a disposable Till key for the engagement
Set the request ceiling from the work plan, then add expiry and optional spend, token, and IP bounds.
-
02
The provider credential stays behind Till
When the project ends, revoke or let expiry stop the key. You do not rotate every connection to recover from one freelancer laptop.
-
03
This is not a secrets-manager replacement
Vaults store keys. They do not end them when the SOW ends. Till is a hosted control layer in front of 12 AI providers, not a general vault, prompt firewall, or compliance certification.
-
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 contractor 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 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.
Share the work. Keep the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.