This might be a dumb question, but I just want to make sure I understand correctly.
I don’t have on-demand spending enabled. So if I exhaust Auto + Composer to 100%, what this is saying is that it will default to API calls until that runs out? Meaning I shouldn’t incur additional charges, correct?
You’re reading it right. With on-demand spending turned off:
Your Auto + Composer usage runs against that pool first.
Once Auto + Composer reaches 100%, additional Auto and Composer 2 requests start drawing from your included API quota (the second bar, ~$70 on your plan).
When the API quota also hits 100% and on-demand is disabled, requests are simply blocked — you won’t be charged anything beyond your subscription.
You’ll see an in-editor notification when you hit the limit, and at that point, you can either enable usage-based pricing or upgrade your plan to keep going. No surprise overage charges if on-demand stays off.
One small nuance: the Auto + Composer → API quota fallback applies when you’re using Auto or Composer. If you explicitly switch to a non-Auto model, that consumption is billed against the API quota from the start.
@watsonbriant One more follow-up! I did a test today and I can confirm one additional piece of info - you can continue to use Composer 2 or Composer 2 Fast after you’ve exhausted the Auto Pool Usage. That composer 2 usage will just draw from the API usage pool instead of the Auto Pool. It’s seamless! No error messages or popup approval.