Caching & versioning

Response	Current cache behavior
Beta logo image	public, max-age=86400, stale-while-revalidate=604800
Generated monogram	public, max-age=3600
Beta JSON and errors	no-store
Published static images	One day
Published manifest	Five minutes

A logo may be updated in place. Conditional GET/HEAD requests use ETags and return 304 Not Modified when the representation is unchanged. Browsers and shared caches can still retain an image during its freshness lifetime; stale-while-revalidate can serve it longer while refreshing. A stable URL is not a promise of immutable content.

Key revocation blocks new API requests after the Worker’s authentication cache expires (up to about 60 seconds). It cannot erase image bytes already held by a browser or shared cache. If you need to check for a correction before the normal cache lifetime ends, revalidate with Cache-Control: no-cache and the returned ETag. Conditional requests still require a valid key.

/v1/ is the current API/storage path version. There is no public deprecation schedule or versioned asset history yet. Be tolerant of additional JSON fields, handle nulls, and do not depend on exact error messages.

If you store copies for an integration, plan a refresh process and review the terms and brand policy. Brand-owner removals and corrections may require your stored copy to change too. Do not republish the collection as a competing catalog or API.