What Is a Churn Feedback API?
A churn feedback API exposes the reasons customers cancel in a structured format that software and AI agents can use. Instead of a founder manually reading cancellation comments, an agent can query recent themes, MRR impact, and examples, then recommend product work.
The API should not just return raw rows. Useful agent APIs summarize, filter, and explain the business impact of the feedback.
Core Resources to Expose
- Accounts/products: which connected Stripe products the key can inspect.
- Churn events: cancellation dates, plan context, churned MRR, and safe subscription metadata.
- Feedback: cancellation reasons and customer comments with redaction boundaries.
- Themes: grouped patterns with counts, recency, and MRR weighting.
- Action plans: agent-ready suggestions for product fixes, experiments, and metrics to watch.
Authentication and Scope Design
Agent keys should be separate from human session tokens. A good v1 key is read-only, revocable, shown once, stored hashed, and optionally scoped to one connected Stripe account. That lets a founder give an agent access to churn context without giving it billing or customer-write powers.
Public examples should always use placeholders like cwk_live_your_agent_key. Never paste real keys into prompts, tickets, screenshots, or public docs.
API vs MCP
Use REST when you are building your own agent runtime, cron, or integration. Use MCP when you want a client like Claude or Cursor to discover tools such as get_churn_themes or generate_retention_action_plan.
ChurnWin supports the same product story through both surfaces: API docs for custom agents and MCP docs for agent clients.