Credits
Shared PC credit balance, consumption, and refunds.
GET /credits/balance returns the account's current PC balance:
{
"object": "credit_balance",
"available_credits": 1200,
"unit": "credits",
"policy": "same_as_pc"
}All valid PC credit grants are treated exactly as the PC product treats them. The API does not create a separate paid-only balance, reservation table, or usage ledger.
When a request is accepted, the existing PC task creation transaction consumes credits. When that task transitions to confirmed failure, the existing PC refund path restores eligible consumed credits exactly once.
Because phase one deliberately avoids changing the shared credit core, a rare race between simultaneous PC and API submissions cannot be fully serialized before Provider submission. Per-user API concurrency and idempotency greatly reduce duplicate API work, but they do not create a cross-channel reservation. A future shared-core reservation refactor is required before high-concurrency general availability.