Keep the forum number in context
The author reports about $150 per month for two years and then $8,600 in MRR after a product change. That is a public self-report, not audited profit or a typical path for every builder.
The change also rests on architecture expertise, accumulated product work, and distribution. A conversational interface did not create those advantages by itself.
Make the rendering task concrete
A customer can understand one prompt that turns a floor plan or reference image into a usable visual direction. Define the input, output, revision limit, and acceptance rule before choosing a model.
A narrow workflow exposes whether the result saves a designer time or merely produces another image to repair. If the user cannot explain what they will do with the output, the product is still too broad.
Measure rework as a real cost
Generation, retries, storage, manual edits, and customer support belong in the delivery cost. A low request price can hide an expensive service when every result needs correction.
Run a small redacted sample with an independent key, a budget limit, and a stop signal. Ask a target user to compare the result with the old workflow before adding features.
Where APIToken fits
APIToken can provide a compatible model entry point, project-level usage records, public status, and a written budget while a rendering workflow is tested.
The source does not show APIToken usage or partnership. The reported MRR remains the author's metric and should not be rewritten as personal income or a promise.