Keys, pools & spend
Your provider keys, the pools that use them in parallel, and the ceilings that keep the bill sane.
4 articles
- Adding your API keysPaste a provider key once; it is encrypted at rest, masked everywhere, and builders use it through a pool by name without ever seeing it.
- Pools: which keys a step usesA pool is a named group of your API keys for one AI provider. Each step picks a pool by name, so nobody building a flow ever handles a key — and you can see whose keys paid for what.
- The daily spend limitOne number that bounds what the whole workspace can spend in any rolling 24 hours — the guard you want in place before anyone else, or any trigger, can start a run.
- Usage and model pricesWhat the workspace is spending — by day, by model, by person — plus the price list behind every estimate, which an admin can correct.