Cap the purchase order. Keep the provider key.

Isolate the PO traffic, not the provider account.

1. 01
   Issue a disposable Till key for the purchase-order job

   Set the request ceiling from expected purchase orders and retries, then add optional token, estimated-spend, expiry, and IP bounds when the purchasing worker needs a tighter envelope.

2. 02
   The provider credential stays behind Till

   The purchase-order 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.

3. 03
   This is not a purchasing system or ERP

   Till does not parse purchase orders, issue POs, or replace your procurement stack. It is a hosted control layer in front of 12 AI providers: a required request ceiling and optional token, spend, expiry, and IP controls.

4. 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.