What problem does it solve? Caching data across Vercel serverless functions, routing middleware, and builds requires understanding a regional, ephemeral cache layer with its own APIs, invalidation semantics, and isolation rules that differ from framework-level caching and ISR. ## Core Features & Use Cases - Runtime Cache Operations: Guides usage of getCache() from @vercel/functions for set, get, delete, and tag-based expiration with TTL and namespacing. - Multi-Layer Invalidation: Explains invalidateByTag and dangerouslyDeleteByTag for purging CDN, Runtime, and Data caches together, plus CLI cache commands. - Next.js Integration: Covers 'use cache: remote' in Next.js 16, updateTag/revalidateTag semantics, and the isolation boundary between Runtime Cache and ISR. - Use Case: A CMS webhook triggers a server action that calls expireTag('blog') so all functions in the region serve fresh content within 300ms. ## Quick Start Ask the AI to add Vercel Runtime Cache caching with tag-based invalidation to an API route using @vercel/functions.