economics

Stripe Meter Export

An endpoint that emits Mission Control's billing_events in Stripe meter_event format, ready for /v1/billing/meter_events.

Mission Control doesn't talk to Stripe directly — keeping the network dependency outside the API surface lets enterprise customers route through their own Stripe Connect billing account, and lets us stay testable without a Stripe test key in CI.

GET /v1/billing/stripe-export returns billing_events as Stripe meter_events: integer cents in payload.value, the org's Stripe customer id from a configured map, and unique idempotency identifiers per mission/event-type pair. A downstream cron / worker POSTs them to https://api.stripe.com/v1/billing/meter_events.

Billing (orchestration + vendor spend)— Mission Control tracks two revenue streams per mission: vendor settlement (x402 to providers) and orchestration fee (to Mission Control).
Orchestration Fee— Mission Control's revenue model: a percentage on top of vendor spend, charged per completed mission.