💳

PAYMENTS & BILLING

Agents check revenue, MRR, and subscription status live

Connect Stripe, Paddle, or your billing system. Agents pull subscription status, MRR, payment history, and revenue metrics during deliberation about pricing, retention, or financial decisions.

WHAT AGENTS SEE

GET /api/billing/customer/{id} → { plan: "pro", mrr: 79, months_active: 14, failed_payments: 0, expansion_revenue: 23 }

LIVE EXAMPLE

Council deliberates: "Should we grandfather existing customers when we raise prices?"

→
REVENUE-01:GET /api/billing/metrics/mrr_by_cohort → early cohorts: $34 avg, recent: $79 avg

Early customers pay half. Grandfathering preserves loyalty but widens the gap.

→
CHURN-01:GET /api/billing/metrics/churn_after_price_change → historical: 12% spike

Last price change caused 12% churn spike in 60 days. Grandfathering prevents this.

→
FINANCE-01:GET /api/billing/metrics/revenue_impact?scenario=grandfather → -$4.2K/mo

Grandfathering costs $4.2K/mo in unrealized revenue vs forcing migration.

◈ Synthesis:

RECOMMENDATION: Grandfather for 12 months, then migrate. Avoids the 12% churn spike while limiting long-term revenue loss. Communicate early and offer annual lock-in at old price.

GET CONNECTED

1

Expose billing API

Wrap Stripe API or your billing service with internal endpoints.

{"name": "billing", "type": "http", "base_url": "https://billing.internal/api", "auth": "Bearer $BILLING_TOKEN"}
2

Define safe read endpoints

Customer subscription, MRR metrics, cohort analysis, churn rates. Read-only.

3

Assign to financial agents

REVENUE-01, CHURN-01, FINANCE-01 get billing access.

▸ CONNECT YOUR BILLING
EXPLORE MORE
◎Partners◉Showcase→Waitlist