Billing & SMS Relay
Hosted billing boundary
Section titled “Hosted billing boundary”Roscoe’s hosted billing and public SMS ingress live on roscoe.sh. The local CLI remains the operator surface and execution engine.
roscoe.sh
Owns the public billing routes, Stripe webhook, consent pages, and Twilio ingress endpoint.
roscoe CLI
Owns lane state, local operator flow, direct Twilio setup, and the live TUI.
K12 Stripe account
Provides the billing primitives behind Roscoe’s hosted subscription flow.
Channel route and hosted relay setup
Section titled “Channel route and hosted relay setup”
When you choose Roscoe-hosted, the normal order is:
- save the phone number
- accept the SMS consent notice
- send the hosted test SMS
- wait for delivery confirmation
- open checkout
- link the current CLI after billing is active
Public endpoints
Section titled “Public endpoints”| Endpoint | Purpose |
|---|---|
/api/relay/healthz | Health and configuration surface for the hosted relay. |
/api/relay/billing/plans | Available Roscoe relay subscription plans. |
/api/relay/billing/status | Current subscription status by phone number. |
/api/relay/billing/checkout-session | Creates a hosted Stripe Checkout Session. |
/api/relay/stripe/webhook | Receives Stripe subscription events for Roscoe relay billing. |
/twilio/sms | Public inbound Twilio webhook route. |
SMS consent and scope
Section titled “SMS consent and scope”Roscoe’s SMS wire is operational only. It is intended for:
- account access and verification
- milestone updates for active work
- review requests or intervention prompts
- account notices tied directly to Roscoe usage
It is not a marketing channel.
See:
Current hosted relay shape
Section titled “Current hosted relay shape”Today, the hosted surface is the public control plane for billing, consent, and ingress. Local Roscoe remains the day-to-day operator interface.
For active lane control, the normal path is still:
- configure Roscoe locally
- launch and monitor lanes from the TUI
- use SMS only when the lane actually needs remote judgment
Operator takeaway
Section titled “Operator takeaway”If you are documenting or supporting Roscoe internally, treat billing and hosted SMS as part of the product boundary, but treat the CLI and TUI as the primary operating surface.