Cap the crew. Keep the provider key.
A swarm, crew, or orchestrated multi-agent job can keep calling a standing provider secret after the planned handoffs have run. Issue a Till key for that job with a required request ceiling so remaining capacity stays readable and the workers can stop.
Isolate the multi-agent traffic, not the provider account.
-
01
Issue a disposable Till key for the multi-agent job
Set the request ceiling from expected planner, worker, and critic 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 multi-agent job uses a Till key, not an unconstrained provider secret in the orchestrator process. When the job is retired, revoke or let expiry stop that key without rotating every connection.
-
03
This is not a swarm runtime or agent host
Till does not orchestrate agents, host a crew, or replace a multi-agent framework. 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 multi-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 swarm host, 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 crew. End the key.
Request Pro beta access. Till is a controlled beta; accounts are onboarded manually. Do not start from self-serve checkout.