Can someone clarify Pro plan usage order? (Auto + Composer → API → On-Demand?)

Support Help
1

Hi everyone,

I’m on Pro and trying to figure out how the usage pools actually work in practice. My dashboard shows:

  • Auto + Composer Usage
  • API Usage

From what I understand (might be wrong):

  • Auto mode, Agent mode, and Composer all share the Auto + Composer pool
  • Once that hits 100%, extra usage might fall through to API quota or On-Demand Spending

I’m not 100% sure though — has anyone figured out the exact order?

What I’m trying to confirm:

  1. If Auto + Composer is maxed out but API Usage still has quota, can you still use Composer/Agent normally?
  2. Does it then pull from the included API Usage first?
  3. After API is gone too, does it switch to On-Demand Spending (if you have that enabled)?
  4. If on-demand is off, do Composer/Agent just stop until the next billing cycle?

My guess for the flow:

Auto + Composer (included) → API Usage (included) → On-Demand Spending (optional) → blocked if nothing left

Would love to hear from anyone who’s hit these limits or knows how it actually behaves. Thanks!

4

Hey, your guess about the overall flow is correct. Point by point:

  1. Yes. Once the Auto + Composer pool is used up, Auto, Agent, and Composer keep working and start using your API quota. The dashboard says it directly: “Consumed by Auto. Additional usage consumes API quota.”

  2. Yes, spillover goes into the included API quota. Key detail: it’s one-way. Usage won’t move back from API to Auto. And if you explicitly pick a named model (not Auto), that usage is charged to the API quota right away and doesn’t touch the Auto + Composer pool.

  3. Yes. When the API pool is also used up, it switches to On-Demand usage-based pricing if it’s enabled.

  4. If On-Demand is off and both pools (Auto + Composer and API) are used up, requests just get blocked until the next billing cycle. Nothing extra is charged.

So your flow is right: Auto + Composer (included) → API (included) → On-Demand (if enabled) → blocked.

One note: Team works differently. It has one shared pool instead of two separate pools with one-way spillover. That one-way spillover behavior is for individual plans. Let me know if anything’s still unclear.