Reference table
| Need | Visual editor | Screenshot API |
|---|---|---|
| One-off manual campaign | Strong fit | Possible, but not the point |
| CI regeneration | Usually manual | Native workflow |
| Agent operation | Difficult | Schema and lint feedback |
| Large localization matrix | Slow to maintain | Request-driven |
The durable artifact
A screenshot editor stores a design state. A screenshot API stores a request contract that can be rerun, reviewed, and changed by code.