MASAKA / Operations / Billing
Operations

One wallet,
verifiable usage.

Browser runtime, model tokens, subscriptions, and one-time boosters settle into one shared organization wallet.

Browser runtime

Capacity is reserved before launch. Metering begins only when the worker reports ready and charges exact running seconds. Failed startup costs nothing; stopping early returns unused reserved credit.

Agent model usage

Each turn records input, cached input, cache-write input, output, and reasoning tokens with the selected priced model. The user-facing charge is five times that model’s API price.

Plans and boosters

ProductBillingCredits
Starter / Pro / MaxMonthly provider-backed checkoutConfirmed payment amount
BoosterOne-time, never renewsDefault $19 or custom $10–$100
Larger top-upContact supportManually arranged above $100
Open billing →

Organization billing

Every project belongs to an organization. Browser reservations and Agent model usage created by active owners, admins, or developers debit that organization wallet atomically. The ledger retains the acting account and project for audit, while the dashboard presents the organization-wide balance and usage history.

  • Owners and admins can buy credits, change plans, and cancel renewals.
  • Developers can spend shared credit through projects they own inside the organization.
  • Viewers can inspect organization state but cannot start billable work.
  • An invited member’s pre-existing personal workspace balance is never merged into another organization.

History and analytics

Dashboard shows subscription state, confirmed past invoices, current draft line items, remaining credit, daily spend, and usage by product. Daily bars support pointer hover, keyboard focus, and click-pinned tooltips; product rows filter the chart.