BytewellsDocs

Billing

Prepaid compute credits, one-off passes from credits, and Stripe subscription rentals.

Bytewells uses three separate money lines. They are not consolidated into one monthly platform invoice.

Compute units (CUs)

Runs consume prepaid compute credits held by Bytewells.

  • Top up via Stripe Checkout (POST /v2/billing/credits/checkout, body { amountUsd } between 5 and 1000).
  • Each run debits the org ledger at $0.15 per CU by default (1 GB × 1 hour, billed per second, 60 s minimum).
  • New accounts get a signup bonus (default $5, configurable). It is compute-only and cannot buy passes.
  • Developers do not share compute revenue.

Without a positive credit balance, non-owner runs return 402 insufficient-credits.

Passes

Coming soon. Short time-window passes (Flash / Burst / Sprint) are not available in production yet; API and pricing details may change before release. See Passes.

When live, time-window passes will be one-off purchases paid from the same prepaid credit balance:

  • No Stripe Checkout and no card confirm at purchase time — suitable for API and agent use (including the MCP server).
  • Bytewells records the developer’s net (after commission and processing costs) in their earnings ledger and pays it in the monthly payout.
  • Not recurring.

Rentals

Monthly rentals are programmatic Stripe Products and Prices created per paid listing.

  • Customer goes through Checkout mode=subscription.
  • Developer-set trial_days (1–30) become subscription_data.trial_period_days. Trials can be card-free; without a payment method at trial end, the subscription cancels.
  • One trial per (listing, renter org), ever.
  • Charged on the Bytewells platform account. Each invoice becomes an entry in the developer’s earnings ledger: commission (default 10%, 0% for developer referrals), Stripe card processing and Stripe Billing fees are deducted at cost. Bytewells pays the fixed Connect fees.
  • Renews monthly until cancelled (POST /v2/me/rentals/:id/cancel).

Paid listings need a supported payout country, not Stripe onboarding. Developers verify with Stripe to be paid; see Publishing for the current country list and our work to expand payouts globally.

Developer payouts

  • Coverage today: the EU, Liechtenstein, Norway, Switzerland, the UK, the United States, Canada, Bosnia and Herzegovina, and Pakistan (see Publishing). Payouts use Stripe Connect on ThoughtPivot, Inc. (US). Global expansion is in progress — more countries will be added as Stripe onboarding allows.
  • Earnings are held 14 days, then payable.
  • One monthly Stripe transfer per developer once the payable balance reaches $50; smaller balances roll over.
  • Refunds reverse the earning proportionally. A dispute freezes the earning until it closes; if lost, it is removed from the developer's balance.
  • Tunables: EARNINGS_HOLD_DAYS, PAYOUT_MIN_CENTS, PAYOUT_DAY_OF_MONTH, UNPAYABLE_GRACE_DAYS, BILLING_FEE_BPS, PASS_PROCESSING_BPS.

Dashboard

  • Billing — credit balance, top-up, Stripe customer portal.
  • Rentals — active subscriptions and trials.
  • Pass settings — opt in to auto-purchase a capped pass when a run would otherwise be blocked (PUT /v2/me/pass-settings).

On this page