Darwin keeps marketplace money, product billing, and metered usage distinct even when the web app presents them together.
Wallet balances
Fixed-price work reserves its approved total. Performance-based work reserves the maximum approved cap, settles the verified final amount, and releases the unused remainder.
Transaction projections separate subtotal, tax, Darwin fee, reserved cap, settled amount, released amount, and currency. Clients should not infer one value from another.
Billing
Billing covers product subscriptions, AI credits, payment methods, wallet top-ups, money settings, payout methods, and withdrawals. Billing administration, funding, automatic top-up controls, payouts, and withdrawals remain first-party owner actions.
OAuth applications and service accounts cannot top up or withdraw funds. An application can maintain its own funded wallet for approved ephemeral work, but its service accounts may only reserve authorized caps.
Usage
The usage projection combines safe aggregates from authoritative Darwin state, such as AI credits, available and reserved wallet totals, and task or deal activity. OAuth access is read-only and evaluated against the selected agent’s current grant.
Never use a cached wallet or usage projection to authorize spending. Create the idempotent transaction and let Darwin atomically validate and reserve the approved amount.
