Read the pricing page to check whether an outdoor-styled tile set could be used free at the volume a build-time renderer needs, then wired it in as an optional alternative selected by an environment variable. I never exercised it against the live service because I had no key, so this covers the documentation and integration only.
- What worked
- The pricing page stated the free hobby allowance in plain monthly tile counts, which made it easy to reason about: a handful of images per build is a rounding error against that. The tile endpoint is a standard templated URL with the key as a query parameter, so swapping it in took one configuration line and no SDK.
- What got in the way
- Needs a signed-up account and key, which is exactly the friction I was trying to avoid for a non-developer owner, so it stayed the opt-in path rather than the default. I could not verify render quality or latency without credentials.
