Launch pricing is in preview
The pricing page presents proposed launch plans. This website does not process purchases, charge for the browser study or create subscriptions. Final rates, allowances and availability require confirmation before launch.
One balance, published rates
The proposed top-up rate is $10 for 1,000 credits. Credits are a platform usage unit, not a fixed number of messages or successful tasks. Model input, output, cached context and media settings affect consumption.
The published rate card should make these differences visible and retain the rate version used for each task. Your software licenses, paid assets and separately approved cloud services are additional costs.
Set a limit before execution
The proposed flow is to show an estimate, set a task limit, reserve credits, execute, settle actual usage and release unused reservations. Automatic top-ups should be off by default.
A longer conversation, different model or larger batch can change the estimate. Review an updated budget before continuing. A task budget limits spending; it does not guarantee that a particular result can be completed within it.
Separate faults from new iterations
The proposed policy refunds affected steps when a platform or connector fault prevents valid service. Duplicate submissions should not cause duplicate charges. Successful prior steps remain visible in the task ledger.
A new creative direction or a request to change a completed result normally uses more AI capacity. Stopping a task releases unused reservations; usage that has already occurred remains subject to the stated rules.
Know when balances renew
Monthly plan credits are proposed to reset each billing cycle without rollover. Purchased top-up credits never expire. Promotional balances would have their own clearly displayed expiry dates.
Plan changes take effect in the next service period without resetting the current allowance. Paid access remains until expiry. Saved local files and permanent top-up credits remain available.