economics

Billing (orchestration + vendor spend)

Mission Control tracks two revenue streams per mission: vendor settlement (x402 to providers) and orchestration fee (to Mission Control).

Every completed mission produces a billing_events row with three amounts: vendor_spend_usd (paid to x402 providers), orchestration_fee_usd (Mission Control's cut), applied_rate (the percentage that produced the fee). The /v1/billing/summary endpoint aggregates by month; /v1/billing/events lists per-mission entries.

Settlement to providers happens via x402 in real-time. Mission Control's fee bills to the customer on a metered basis — typically into Stripe, via the /v1/billing/stripe-export adapter.

Orchestration Fee— Mission Control's revenue model: a percentage on top of vendor spend, charged per completed mission.
Stripe Meter Export— An endpoint that emits Mission Control's billing_events in Stripe meter_event format, ready for /v1/billing/meter_events.