playbook/antigravity-awesome-skills/skills/vercel-optimize/references/support-topics/next-route-handler-get-cache-defaults.md

id	title	status	candidateKinds	frameworks	priority	citations	maxBriefChars
next-route-handler-get-cache-defaults	Next.js Route Handler GET cache defaults	active	uncached_route cache_header_gap	next@>=15.0.0	91	https://nextjs.org/docs/app/api-reference/file-conventions/route https://vercel.com/docs/caching/cdn-cache	850

Investigation Brief

On Next.js 15+, GET Route Handlers are dynamic by default. For hot public GET handlers, verify whether uncached behavior is intentional before recommending cache headers or route config.

Evidence To Check

Use method share, cache result, and source. Check GET, revalidate, dynamic, request headers, cookies, auth, query params, and response Cache-Control.

Do Not Recommend When

Do not cache POST-style handlers, webhooks, per-user APIs, streaming responses, search requests with user-specific params, or handlers that read auth/cookies.

Verification

Name the Next.js version, GET share, cache result mix, and the exact handler or header line that makes public caching safe.