Funds credits
Provider reference, settlement asset, amount, webhook event, credit entitlement, funded account, credits funded, and release policy.
Settlement receipts · credit funding rail
Settlement receipts fund the credit ledger.
A settlement receipt records the provider confirmation that funds an agent credit entitlement. It is the money-side receipt. Usage receipts stay separate and record what Wever Labs OS consumed when work ran.
Clean accounting split
Two receipts. One operating trail.
The settlement receipt answers: what funded the credits? The usage receipt answers: what work consumed the credits? The result contract carries both.
Consumes credits
Task run, work order, credits debited, remaining credits, result status, evidence state, and callback status.
Returns the trail
One downstream-readable envelope linking funding, usage, result, attestation, ledger, callback, and next action.
Receipt object
The provider-side record is explicit.
The settlement receipt is shaped for Stripe stablecoin, x402, Circle / USDC, manual invoice, and provider tracks while preserving one credit ledger center.
{
"receipt_type": "agent_settlement_receipt",
"settlement_provider": "stripe_stablecoin",
"settlement_status": "credits_funded",
"credits_funded": 25,
"usage_receipt_policy": "usage_receipts_record_credits_consumed_after_work_runs"
}
Settlement support
Settlement receipts sit inside the OS support object.
The settlement receipt funds credits. The usage receipt records credit consumption. The rail binding ties both to the task lifecycle, result contract, callback state, and console snapshot.
Settlement to result
The rail does not stop at payment.
Credits fund the run, the OS performs the work, usage gets receipted, the result contract points to every proof object, and the callback returns the state to the requesting agent.