Problem
The Switchboard 2-SKU economic model specifies Hosted Switchboard with two tiers (Standard, Pro) plus per-tx overage. Today the OSS lib is self-hostable but there is no managed control plane that a customer can point a checkout flow at. To onboard the first Hosted customers (IPTO PI per #82, Hanzo enterprise per #81, others), we need the billing surface live.
This issue tracks the productized billing surface itself, not any individual customer onboarding.
Proposed Approach
- Customer onboarding flow:
- Sign-up endpoint that issues an API key + endpoint URL
- Tier selection (Standard / Pro) at sign-up; tier change requires support ticket (no self-serve downgrade)
- Month-to-month default; annual option for Pro at a 10% discount
- Metering:
- Per-tx counter incremented on every
x402_middleware.settle and AgentEscrow.release event
- Overage line item: tx count above the included tier minute at
$0.001/tx
- Invoicing:
- Monthly via Stripe (or a paid-billing provider already in the stack)
- Pro annual customers get a single annual invoice with 10% off
- Customer dashboard:
- No public pricing page. Per the kcolbchain pricing-private convention, prospects get pricing on application via the standard contact flow. The billing system enforces the tier numbers; the public surface does not display them.
Acceptance Criteria
References
Problem
The Switchboard 2-SKU economic model specifies Hosted Switchboard with two tiers (Standard, Pro) plus per-tx overage. Today the OSS lib is self-hostable but there is no managed control plane that a customer can point a checkout flow at. To onboard the first Hosted customers (IPTO PI per #82, Hanzo enterprise per #81, others), we need the billing surface live.
This issue tracks the productized billing surface itself, not any individual customer onboarding.
Proposed Approach
x402_middleware.settleandAgentEscrow.releaseevent$0.001/txAcceptance Criteria
References