Add AI Monetization group to Use Cases

[ryanechternacht]

What

Takes the Use Cases section further to align with the runtime monetization / monetize-AI marketing direction. Keeps the existing four buckets, weaves AI framing in, and adds a dedicated AI group that leads the section.

Changes

New "AI Monetization" group (leads the section) — four pages, written in the established skeleton (need → common approaches → how Schematic fits in → learn more):

• Show customers what an action will cost — pre-flight cost previews (protect from surprise bills)
• Warn customers before they hit a limit — surprise-throttle protection: soft warnings at 70/80/90%, grace periods
• Protect your margins — runtime enforcement as margin defense
• Meter on a real-time credit ledger — exactly-once/idempotent ledger, holds → commit → release

Cross-listing — each AI page is surfaced in its natural bucket too (pre-flight + ledger → PLG, throttle → Customer Management, margins → Operations) via nav links, so it's one page with two entry points.

Reframes

• Stripe sync → "Keep your billing system in sync" with Metronome alongside Stripe ("keep your billing system, no migration").
• AI-native examples (tokens, agent runs) woven into the usage and credit pages.
• Index intro now leads with monetizing AI and usage-based products.

Notes

• These pages describe near-term roadmap capabilities (pre-flight endpoint, holds, grace periods, Metronome) per the new positioning. The API spec already carries a getCreditLedger endpoint. If you'd prefer, I can mark the not-yet-GA pages hidden: true until they ship.
• fern check: 0 errors; no new warnings from these pages.

🤖 Generated with Claude Code

[github-actions]

🌿 Preview your docs: https://schematic-preview-7813d1e6-f82f-40d2-9756-370a756e0566.docs.buildwithfern.com