Home/Journal/How credits and your own account actually settle
EVIDENCE NOTES

How credits and your own account actually settle

Shipsite bills a user-requested task once. It shows an estimate, reserves a maximum, then settles orchestration plus any Shipsite-paid provider cost. Unused reservation returns. A verified path on your own account adds no provider-cost credits. Shipsite never takes a percentage of your key.

Mengjian / Xiaomo
01

The billing unit is a task, not a token

Internal retries, stage records, and tool traces are evidence that the task ran. They are not extra line items. Automatic recovery stays inside the original reservation. A rerun you request is a new task and gets a new estimate.

02

Reservation is a ceiling

Before model or paid-data work starts, Shipsite shows the estimate and reserves a model-aware maximum. Settlement cannot climb above that cap after the fact. If the task fails before useful execution, the reservation is released according to the task rule.

03

Your key pays the model; credits pay the factory

When a verified user-owned account pays OpenAI, Anthropic, or another provider directly, Shipsite does not invent a provider-cost credit line for that usage. The execution service fee remains, because contracts, quality checks, storage, retries, and handoff still run on Shipsite. There is no extra surcharge for using your own account, and no percentage skim.