playbook/antigravity-awesome-skills/skills/vercel-optimize/references/support-topics/external-api-critical-path.md

id	title	status	candidateKinds	frameworks	priority	citations	maxBriefChars
external-api-critical-path	External API critical path	active	external_api_slow	next@>=13.0.0	90	vercel-react-best-practices:async-parallel vercel-react-best-practices:server-parallel-fetching vercel-react-best-practices:server-cache-react	850

Investigation Brief

For external API candidates, identify the customer route that waits on the slow hostname and whether the call is on the critical path.

Evidence To Check

Use callers-by-route evidence, transfer size, and source awaits. Check whether the upstream call can run in parallel, be cached safely, be reduced in payload size, or move after response.

Do Not Recommend When

Do not cache mutations, secrets, per-user responses, or upstream calls whose freshness requirement is unknown.

Verification

Name the hostname, caller route, p75 or p95 latency, and the exact source line that waits on the call.