Vercel Blob now supports consistent reads on private storage
Vercel Blob ships consistent reads for AI agents. Memory files, transcripts, and session data now reflect latest writes—no stale cache.
Why it matters
As AI agents proliferate in production, infrastructure primitives like consistent reads become critical. Vercel's update addresses a real pain point for agent-backed applications that need fresh state on every read.
The key facts
8 to knowVercel Blob adds useCache: false parameter for consistent reads
Stale cache window on overwrites: up to 60 seconds
Use case: agent memory files, session transcripts, scheduled JSON reports
Consistent reads bypass CDN, incur Fast Origin Transfer cost
Feature available in latest @vercel/blob SDK
Vercel Blob now supports useCache: false parameter for consistent reads
Cached reads show stale data for up to 60 seconds on overwrites
Consistent reads bypass CDN, incur Fast Origin Transfer costs
Go to the source
Vercel Blogvercel.com
Publisher excerpt: now supports consistent reads on private storage. Pass to or for a read that reflects the latest write.Vercel BlobuseCache: falseget()presignUrl() A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing…