Publish current plans and billing guide

[charlesrhoward]

Summary

• replace the billing placeholder with current Individual plans, prices, hosted usage rates, and add-ons
• document inference-credit behavior, parallel-run capacity, payment methods, invoices, and role limits
• add billing support routing and correct the docs repository link

Verification

• pnpm lint
• pnpm types:check
• pnpm test
• pnpm build

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mogplex-docs	Ready	Preview	Aug 18, 2026 7:04pm

[mogplex]

Mogplex PR Review

Status: Attention needed

This is a clean, well-structured documentation PR that replaces the billing placeholder with real plan details, pricing tables, usage rates, and billing support routing. The pricing math is internally consistent (15% annual discount across all three plans), inference credit purchases are 1:1, and all internal links are valid. The settings.mdx update correctly hands off to the new billing page. One inconsistency: support.mdx still has the old docs repo link in the symptom table after the PR corrected it in the "Docs issues" section of the same file.

1 finding was added inline.

View check run

[mogplex]

Warning: Incomplete docs repo link correction in support.mdx

The PR description says it corrects the docs repository link, and the diff does change one occurrence in the "Docs issues" section from webrenew/mogplex-docs to Mogplex/docs. However, the same file's symptom table still contains the old link: [Docs source](https://github.com/webrenew/mogplex-docs) on the "A doc link or claim looks wrong" row (line 15 in the symptom table). This leaves the file inconsistent — two references to the docs repo, one pointing to Mogplex/docs and one still pointing to webrenew/mogplex-docs. Users following the symptom table link will land on the wrong repository. Since this PR's scope explicitly includes correcting the docs repo link and it touches this exact section of the file, the second occurrence should be updated in the same change.