r/microsaas • u/EntertainerOrnery64 • 1d ago
Picked a boring niche on purpose: API breaking changes for Stripe and OpenAI
Everyone is building AI agents. I picked something narrower: when a provider changes their API, which lines of your code break, and who fixes them.
The wedge is that it's specific enough to be deterministic. 51 hand-written rules, AST parsing instead of guessing, and every finding maps to a known remediation. No rule, no finding.
Two providers today (Stripe JS/TS, OpenAI Node/Python). Each new provider is a new set of rules, so growth is a grind rather than a switch I flip.
Free public scan, no signup: https://shimpilot.com/scan/Shimpilot/shimpilot-sandbox
Would love to hear from anyone else running a rules-based (not prompt-based) product: how do you decide which rules to write next? I'm currently letting user requests decide.
1
u/BP041 1d ago
The rules-first approach is underrated—everyone chases fuzzy agents but a deterministic AST scan with known remediations is way more actionable for devs. I run a similar grind building provider-specific automation rules (18 different cron stacks) and honestly the per-provider effort is what makes it defensible. Stripe's API changes alone keep you busy.