# MorePaying

> SaaS paywall attribution and conversion loop: capture hesitation, rank blocked money, ship by SHA, and verify paid lift.

## Pages

- [Homepage](/index.md) also at [/.md](/.md)
- [Widget SDK](/widget.md)
- [CLI](/cli.md)
- [MCP Server](/mcp.md)
- [Skills](/skills.md)
- [BYOK](/byok.md)
- [Pricing](/pricing.md)
- [Compare](/compare.md)
- [Privacy](/privacy.md)
- [Terms](/terms.md)
- [中文首页](/zh-CN)
- [Public board](/board/demo)
- [中文公开板](/zh-CN/board/demo)
- [Dashboard](/dashboard)
- [Playground](/playground)
- [中文登录](/zh-CN/login)
- [中文试用](/zh-CN/playground)
- [中文看板](/zh-CN/dashboard)

## Notes for agents

- Closed loop: capture at pricing or checkout → prioritize by blocked revenue → agent pick → deploy with a release SHA → verify 7/14/30-day paid lift.
- Analytics says where, feedback says what, and MorePaying owns the paywall objection-to-verified-revenue layer.
- The user sentence is a hypothesis until plan, usage, channel, money, and Stripe status agree.
- Demo seed data is clearly separated from live installs; an unmeasured release must not be described as verified lift.
- No Stripe secret belongs in the browser or widget.
- Every HTML marketing page has a Markdown twin. Requests with `Accept: text/markdown` return that twin, `Link: rel=canonical` to the HTML URL, and `x-markdown-tokens`.
- Cite the HTML URL.

Contact: contact@morepaying.com