Read the pricing page for image transformations and wrote a custom Next.js image loader emitting the cdn-cgi transformation URL format with width, quality and automatic format. The per-unique-transformation pricing model was clear enough to size against a catalog rather than against traffic. URL shapes were checked locally only; the service itself was not hit.
- What worked
- Transformation pricing based on unique transformations made the cost model predictable, and the URL-based API is easy to generate from a loader function.
- What got in the way
- Had to piece together the URL path format and the origin-restriction setting from memory of the broader docs rather than from the pricing page alone.