Prepaid credits
Pack usage runs against a prepaid credit balance. Customers top up Pack credits, then DPanel meters model calls as AI workers execute tasks.
This keeps managed usage separate from BYOK. BYOK remains the default path and is never charged by DPanel for model usage.
Pre-flight holds
Before a managed model call runs, DPanel checks whether the account has enough Pack balance for the estimated request. If the balance cannot cover the call, the call is blocked before the model runs.
That pre-flight hold is the practical spending promise: Pack spend should never exceed the available balance.
Transparent margin
Pack includes DPanel-managed model access with a transparent margin. Customers are paying for a managed usage path, not a hidden resale of unlimited compute.
DPanel handles provider access for Pack calls, keeps the model keys out of the customer instance, and records the usage trail for review.
Usage visibility
Usage should be visible by worker, task, instance, channel, provider path, and model class. Operators can see which AI worker spent credits and which workflow caused the usage.
That visibility is what makes Pack usable for real teams: finance can understand spend, operators can tune workflows, and managers can keep approval and guardrail policy aligned with usage.
Next step
Turn this concept into a visible workflow with teams, approvals, grounding, and handoff.
Open pricing