Sanity API CDN staleness vs live queries for a low-traffic site
Goal We run a low-traffic marketing site backed by a single Sanity dataset (assume a current Sanity v3-era project and a static frontend). To stay within free-plan API allowances, we want to cut runtime API usage as much as possible without breaking the editing experience. Constraints and uncertainty The documented options seem to be: query the cached CDN en
sanity