Skip to content

Pooled credits and caps

How the shared credit pool is funded, how allocation to a client works, why an idempotency key is required, and how per-client caps protect your margin.

Reseller and agency accounts only

All your clients' AI usage is funded from one pool held by your organisation. Your reseller plan tops it up; you hand out portions of it.

Funding the pool

Each paid reseller invoice grants that tier's pooled credits to your organisation. An annual prepay grants the whole year up front. Cancelling clears the plan and drops seats to zero, but the pool balance remains until spent.

The reseller panel shows the pool balance and seats used against total.

Allocating to a client

In a client's row, enter an amount and choose Allocate. That:

  1. 1
    debits your pool,
  2. 2
    credits the client's workspace,
  3. 3
    and switches credit metering on for that client, so the credits are

    actually consumed by their chatbots.

Allocation is blocked when the pool is too low — raise your tier to top up.

Warning:

An idempotency key is required on every allocation. The dashboard supplies one; a direct API call must send Idempotency-Key (or an idempotencyKey body field, 8–128 characters). Without one the request is refused:

An idempotency key is required for credit allocations.

That requirement exists so a retried request can never double-debit your pool.

Per-client spend caps

Set a monthly credit cap per client so no single client can burn the pool. Leave it blank to clear the cap.

A cap is the difference between a busy client and a runaway one. Set caps proportional to what each client pays you, and revisit them when you change a client's price.

When a client runs out

The client's assistant pauses for visitors with a friendly message, and human handoff keeps working — see Credits and top-ups for exactly what a visitor sees. Resolve it by allocating more from the pool.

Because burn alerts follow the pooled grant, you get the same 50/80/100% ladder against the pool that a direct customer gets against their allowance.

Margin in practice

You charge each client what their support is worth, draw all of their usage from one flat-fee pool, and keep the difference. Credits are metered to real provider cost with a floor, so a pooled tier's included usage stays below its fee. The per-client caps are what keep that arithmetic true when one client's volume spikes.

Where to go next

Last updated