Workflow-first MVPDocs Center liveHelp routes reservedProjects & Billing in codeSupply & Marketplace in code

Billing

Billing now acts as the Day 4 commercial source of truth: subscription posture, included credits, accepted execution reservations, usage, and future settlement rules all stay aligned here before any live payment provider is connected.

Help Center Docs Center

Billing Overview

Billing now anchors the subscription, credit, and usage relationship

This page still avoids live payment collection, but Module 5 Day 4 now turns Billing into the shared commercial source of truth: subscription posture, included credits, accepted execution reservations, and downstream settlement all read from one model.

Service boundary: foundation-control-plane-service

State demoLive Empty Error

Module 5 Day 4 shipped

Available

432

Reserved

Hold

Settlement threshold

100 CNY

Balance buckets

Keep plan balance, reserved execution cost, and settlement hold visible before live payments are turned on.

Growth launch plan

Included plan credits

included

500

Reference growth allowance used to demonstrate how accepted execution, reservation, and usage share the same commercial surface.

Available credits

bonus

432

Spendable reference balance after accepted execution reservations and settlement hold are already reflected in the current growth posture.

Reserved credits

reserved

Credits already reserved by accepted executions that passed identity, account, account_state, plan, project, and action checks.

Settlement hold

hold

Provider-side accounting held after accepted usage exists and before any future payout release.

Commercial relationship map

Day 4 fixes the relationship between subscription posture, credits, accepted execution, and usage before real billing enforcement starts.

Shared foundation truth

Subscription posture

account entitlement

Subscription posture unlocks capability bands and refills the baseline credit budget at the account boundary.

The subscription decides whether the account is active and what paid surfaces are allowed, but accepted execution still becomes billable through credits and usage instead of a hidden plan-only switch.

Upstream

identity -> billing account -> account stateplan capability

Downstream

included credits become wallet balanceaccepted execution can reserve credits only when the plan allows it

Surface: /workspace/billing

Credit wallet

account-owned wallet

Credits remain the spendable unit for accepted execution whether the operator calls the run a test or production.

Wallet state is account-owned, but the console must stay project-filterable so teams can explain where reserved, consumed, and held balance moved without splitting the billing account.

Upstream

included subscription creditsmanual grants or future top-ups

Downstream

reservation at accept-runconsumption, release, or settlement hold after execution

Surface: /workspace/billing

Accepted execution bridge

project execution -> account billing bridge

Accepted execution is the moment a project-scoped workflow becomes a commercial event.

Preview stays free. Once a run is accepted, the workflow keeps its project ownership, reserves account credits, and becomes the first durable receipt that usage and settlement can build on.

Upstream

workflow / project / object ownershipcredit gate after permission order passes

Downstream

queued run receiptusage reservation and later terminal usage evidence

Surface: /workspace/usage

Usage ledger

account ledger with project filters

Usage is the durable ledger story that ties reservation, consumption, and future settlement holds together.

Usage rows stay readable by project even when the underlying wallet is account-owned, so operators can audit accepted execution, later settlement, and commercial exceptions from one place.

Upstream

accepted execution receiptreservation / completion / settlement events

Downstream

billing overview and audit reviewfuture settlement eligibility and payout release

Surface: /workspace/usage

Recent billing events

This event list is reserved for accepted runs, grants, holds, and later invoice or payout evidence.

EventKindAmountCreated

Selected event

Autofill accepted execution reserved credits

2026-03-25 08:35

reserved

Amount

-12

Detail

A queued autofill run reserved credits only after project, object, action, and plan checks had already passed.

Plan posture

Subscription relationship

Subscription posture unlocks capability bands and refills the baseline credit budget at the account boundary.

Billing state

active

Next invoice

2026-04-25

Payout provider

manual_review

Current rules

Subscription unlocks capability, credits fund execution

The current account root is on the growth plan, so billing overview now follows the shared foundation account plan instead of static mock subscription copy.

Growth unlocks accepted execution

Growth enables the same accepted execution lane enforced by accept-run today. Credits can reserve only after identity, account, account_state, plan, project, and action checks all pass.

Testing is not a billing bypass

Any accepted execution should consume the same credit unit whether it is marked as test or production.

Reserve before execution

Credits should be checked and reserved after permission checks but before the browser or MCP runner starts.

Settlement ledger before payout

Provider revenue share must be written to a settlement ledger before a payout threshold can release funds.

Billing ledger Settlement Usage ledger

Credit lifecycle

Included

grant

Subscription or owner grant establishes the baseline credit budget.

The account starts from included plan credits or explicit grants before any project accepts a billable execution.

Available

grant / invoice

Available balance is the spendable portion after existing reservations and holds.

Billing overview surfaces the balance that can still fund new accepted runs without hiding earlier queued reservations or settlement windows.

Reserved

reserved

Accepting a run reserves credits before the runner starts.

Reservation happens only after the permission ladder and ownership checks pass, so queued execution is already commercially visible before terminal work begins.

Consumed

accepted

Terminal execution settles reserved credits into real usage.

Completion converts the earlier reservation into a durable usage receipt without charging the customer a second time.

Hold

hold

Provider or marketplace revenue effects move into a hold window after usage exists.

Future revenue-share or payout logic should derive from accepted usage and a hold period instead of bypassing the customer ledger with a separate hidden path.

Module 5 accepted

The developer, marketplace, and settlement entry surfaces are now explicit on top of the same billing foundation. The next real implementation priority is organization, members, and permissions first, before live billing enforcement expands.