Credits and transactions
Inspect available credits, financial holds, allocation provenance and expiration.
Read the complete balance
GET https://api.ndnci.com/v1/balance requires billing:read and returns:
totalMillicents: currently held credits before subtracting active reservations.reservedMillicents: credits committed to admitted work that has not settled.spendableMillicents: credits currently available to admit another operation.allocations: a bounded page of credit sources, remaining amounts, creation timestamps and expiration dates.
Allocation provenance distinguishes how credits entered the workspace's pool. Preserve the returned expiration timestamp; a nonexpiring allocation has expiresAt: null. Follow nextCursor to inspect additional allocations.
All monetary amounts are integers in millicents. Usage points have separate counters and do not appear as purchased credit allocations.
Read the ledger
GET https://api.ndnci.com/v1/transactions returns a bounded ledger page. Amounts are signed: usage removes credits, while a credit purchase or an eligible refund increases them.
A transaction can reference a job and its known executionOrigin. The Web, REST API and MCP draw on the same selected workspace's credit pool. null origins on historical transactions indicate that attribution was not recorded at the time.
Estimates, maximums and actual charges
An estimate describes expected and maximum cost. Acceptance of costly work reserves its bounded maximum; settlement records consumed work and releases unused amounts.
A provider request may incur a cost even when the overall job fails or is cancelled after the provider accepts it. Retry checkpoints prevent completed stages from being charged again where the operation supports resumable execution.
Set financial budgets as an additional ceiling for each key and the combined workspace automation pool. A budget is distinct from the workspace's remaining credit balance.