summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroboeve[bot] <311457182+roboeve[bot]@users.noreply.github.com>2026-10-28 19:17:26 +0000
committerGitHub <noreply@github.com>2026-10-28 19:17:26 +0000
commit69b4772c5e25a42c3e6ede7f17e3ad87d1674ac4 (patch)
tree3b58d1fa1fabf5a2e288d71b28238b63920035fe
parent1a2c79d4e6c4a2283dc2c614b6538cbe1ed5ca62 (diff)
fix(vercel-optimize): handle CDN Requests rename and Flat Rate CDNvercel-optimize/cdn-requests-rename
-rw-r--r--packages/vercel-optimize-tests/test/cost-coverage.test.mjs6
-rw-r--r--packages/vercel-optimize-tests/test/new-gates.test.mjs23
-rw-r--r--skills/vercel-optimize/lib/cost-coverage.mjs7
-rw-r--r--skills/vercel-optimize/lib/display-labels.mjs2
-rw-r--r--skills/vercel-optimize/lib/gates/platform-bot-protection.mjs7
-rw-r--r--skills/vercel-optimize/lib/gates/uncached-route.mjs2
-rw-r--r--skills/vercel-optimize/lib/scanners/force-dynamic.mjs2
-rw-r--r--skills/vercel-optimize/lib/scanners/middleware-broad-matcher.mjs2
-rw-r--r--skills/vercel-optimize/references/candidates.md4
-rw-r--r--skills/vercel-optimize/references/docs-library.json8
-rw-r--r--skills/vercel-optimize/references/doctrine.md2
-rw-r--r--skills/vercel-optimize/references/playbooks/README.md2
-rw-r--r--skills/vercel-optimize/references/playbooks/ai-application.md4
-rw-r--r--skills/vercel-optimize/references/playbooks/api-service.md2
-rw-r--r--skills/vercel-optimize/references/playbooks/content-site.md2
-rw-r--r--skills/vercel-optimize/references/playbooks/ecommerce.md4
-rw-r--r--skills/vercel-optimize/references/playbooks/marketing.md4
-rw-r--r--skills/vercel-optimize/references/playbooks/saas.md4
-rw-r--r--skills/vercel-optimize/references/playbooks/sveltekit.md2
-rw-r--r--skills/vercel-optimize/references/scanner-patterns.md4
-rw-r--r--skills/vercel-optimize/references/scoring.md20
-rw-r--r--skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md6
-rw-r--r--skills/vercel-optimize/references/voice.md2
23 files changed, 82 insertions, 39 deletions
diff --git a/packages/vercel-optimize-tests/test/cost-coverage.test.mjs b/packages/vercel-optimize-tests/test/cost-coverage.test.mjs
index f779a75..dd34d03 100644
--- a/packages/vercel-optimize-tests/test/cost-coverage.test.mjs
+++ b/packages/vercel-optimize-tests/test/cost-coverage.test.mjs
@@ -11,6 +11,12 @@ test('classifyService: covered services map to their dimension', () => {
assert.deepEqual(classifyService('ISR Reads', allDims), { covered: true, dim: 'isr' });
});
+test('classifyService: CDN Requests (renamed from Edge Requests) stays covered', () => {
+ assert.deepEqual(classifyService('CDN Requests', allDims), { covered: true, dim: 'edge-requests' });
+ assert.deepEqual(classifyService('CDN Request CPU Duration', allDims), { covered: true, dim: 'edge-requests' });
+ assert.deepEqual(classifyService('Edge Requests - Additional CPU Duration', allDims), { covered: true, dim: 'edge-requests' });
+});
+
test('classifyService: uncovered services flagged with family', () => {
const sandbox = classifyService('Sandbox Provisioned Memory', allDims);
assert.equal(sandbox.covered, false);
diff --git a/packages/vercel-optimize-tests/test/new-gates.test.mjs b/packages/vercel-optimize-tests/test/new-gates.test.mjs
index 216ce9e..596632c 100644
--- a/packages/vercel-optimize-tests/test/new-gates.test.mjs
+++ b/packages/vercel-optimize-tests/test/new-gates.test.mjs
@@ -297,3 +297,26 @@ test('platform_bot_protection: when BotID is enabled, no candidate regardless of
};
assert.deepEqual(botGate(signals), []);
});
+
+for (const name of ['CDN Requests', 'Edge Requests']) {
+ test(`platform_bot_protection: reads billed cost from the "${name}" usage line`, () => {
+ const signals = {
+ project: { security: { botIdEnabled: false, managedRules: {} } },
+ usage: { services: [{ name: 'CDN Request CPU Duration', billedCost: 1 }, { name, billedCost: 60 }] },
+ metrics: { requestsByRouteCache: { rows: [{ route: '/', cache_result: 'MISS', value: 1000 }] } },
+ };
+ const out = botGate(signals);
+ assert.equal(out.length, 1);
+ assert.equal(out[0].evidence.edgeCost, 60);
+ assert.match(out[0].o11ySignal, /edge_cost=60/);
+ });
+}
+
+test('platform_bot_protection: CDN Request CPU Duration alone is not treated as request cost', () => {
+ const signals = {
+ project: { security: { botIdEnabled: false, managedRules: {} } },
+ usage: { services: [{ name: 'CDN Request CPU Duration', billedCost: 60 }] },
+ metrics: { requestsByRouteCache: { rows: [{ route: '/', cache_result: 'MISS', value: 1000 }] } },
+ };
+ assert.deepEqual(botGate(signals), []);
+});
diff --git a/skills/vercel-optimize/lib/cost-coverage.mjs b/skills/vercel-optimize/lib/cost-coverage.mjs
index 09a8b19..a3a500d 100644
--- a/skills/vercel-optimize/lib/cost-coverage.mjs
+++ b/skills/vercel-optimize/lib/cost-coverage.mjs
@@ -6,8 +6,9 @@ const SERVICE_DIMENSION = [
{ match: /^Function Invocations$/i, dim: 'function-duration' },
{ match: /^Fluid Active CPU$/i, dim: 'function-duration' },
{ match: /^Fluid Provisioned Memory$/i, dim: 'function-duration' },
- { match: /^Edge Requests$/i, dim: 'edge-requests' },
- { match: /^Edge Requests.*Additional CPU Duration/i, dim: 'edge-requests' },
+ // "Edge Requests" was renamed "CDN Requests" (Sept 2026). Match both so older billing windows still classify.
+ { match: /^(?:Edge|CDN) Requests$/i, dim: 'edge-requests' },
+ { match: /^(?:Edge|CDN) Requests?\b.*CPU Duration/i, dim: 'edge-requests' },
{ match: /^Edge Function Execution Units$/i, dim: 'edge-requests' },
{ match: /^Edge Middleware Invocations$/i, dim: 'edge-requests' },
{ match: /^ISR (Reads|Writes)$/i, dim: 'isr' },
@@ -126,7 +127,7 @@ export function renderCostCoverageMarkdown(coverage) {
lines.push('');
const coveredPct = totalBilled > 0 ? (coveredBilled / totalBilled) * 100 : 0;
const uncoveredPct = totalBilled > 0 ? (uncoveredBilled / totalBilled) * 100 : 0;
- lines.push(`This audit has metric coverage for **$${coveredBilled.toFixed(0)} (${coveredPct.toFixed(0)}%)** of this bill via function-duration, edge-requests, ISR, middleware, and image-optimization dimensions. **$${uncoveredBilled.toFixed(0)} (${uncoveredPct.toFixed(0)}%)** sits in billed areas this run cannot analyze safely, including the top actionable items below:`);
+ lines.push(`This audit has metric coverage for **$${coveredBilled.toFixed(0)} (${coveredPct.toFixed(0)}%)** of this bill via function-duration, CDN requests, ISR, middleware, and image-optimization dimensions. **$${uncoveredBilled.toFixed(0)} (${uncoveredPct.toFixed(0)}%)** sits in billed areas this run cannot analyze safely, including the top actionable items below:`);
lines.push('');
lines.push('| Service | Billed | Share | Family | Coverage |');
lines.push('|---|---|---|---|---|');
diff --git a/skills/vercel-optimize/lib/display-labels.mjs b/skills/vercel-optimize/lib/display-labels.mjs
index e8f90f8..740959a 100644
--- a/skills/vercel-optimize/lib/display-labels.mjs
+++ b/skills/vercel-optimize/lib/display-labels.mjs
@@ -44,7 +44,7 @@ const SIGNAL_LABELS = new Map([
['ratio', 'ratio'],
['host', 'host'],
['calls', 'external API calls'],
- ['edge_cost', 'Edge Request cost units'],
+ ['edge_cost', 'CDN Request cost units'],
['bot_protection', 'Bot Protection'],
['bot_fdt_pct', 'bot Fast Data Transfer share'],
['LCP', 'Largest Contentful Paint (LCP)'],
diff --git a/skills/vercel-optimize/lib/gates/platform-bot-protection.mjs b/skills/vercel-optimize/lib/gates/platform-bot-protection.mjs
index 035f063..30e1868 100644
--- a/skills/vercel-optimize/lib/gates/platform-bot-protection.mjs
+++ b/skills/vercel-optimize/lib/gates/platform-bot-protection.mjs
@@ -12,7 +12,7 @@ export const metadata = {
scope: 'account',
sourceCitation: 'vercel-optimize gate threshold',
description:
- 'When BotID is disabled AND there is evidence (observed bot bandwidth share, edge cost, or substantial request volume) that bot traffic is non-trivial. Bot traffic inflates edge request counts without delivering user value; staged bot protection can reduce waste on bot-heavy projects. Skipped on quiet projects with no bot evidence — the recommendation would be noise.',
+ 'When BotID is disabled AND there is evidence (observed bot bandwidth share, CDN request cost, or substantial request volume) that bot traffic is non-trivial. Bot traffic inflates CDN request counts without delivering user value; staged bot protection can reduce waste on bot-heavy projects. Skipped on quiet projects with no bot evidence — the recommendation would be noise.',
};
export function gate(signals) {
@@ -30,7 +30,8 @@ export function gate(signals) {
const totalRequests = totalRequestsFromSignals(signals);
const botShare = computeBotShare(signals);
const edgeService = (signals.usage?.services ?? []).find(
- (s) => /edge.request/i.test(s.name ?? '')
+ // Billing name is "CDN Requests" since Sept 2026; older windows say "Edge Requests".
+ (s) => /^(?:edge|cdn)[ -]requests?$/i.test(s.name ?? '')
);
const edgeCost = edgeService?.billedCost ?? null;
@@ -71,7 +72,7 @@ export function gate(signals) {
: 'BotID disabled with observable traffic',
question: botShare?.botPct != null && botShare.botPct > 0.2
? `Bot traffic accounts for ${(botShare.botPct * 100).toFixed(0)}% of FDT bytes (top category: ${botShare.topCategory ?? 'unknown'}). Would enabling BotID + a challenge rule reduce that share?`
- : 'Would enabling BotID (Bot Protection) reduce edge request volume from automated traffic?',
+ : 'Would enabling BotID (Bot Protection) reduce CDN request volume from automated traffic?',
evidence: {
botEnabled: false,
edgeCost,
diff --git a/skills/vercel-optimize/lib/gates/uncached-route.mjs b/skills/vercel-optimize/lib/gates/uncached-route.mjs
index 3898f59..73be97f 100644
--- a/skills/vercel-optimize/lib/gates/uncached-route.mjs
+++ b/skills/vercel-optimize/lib/gates/uncached-route.mjs
@@ -14,7 +14,7 @@ export const metadata = {
scope: 'route',
sourceCitation: 'vercel-optimize gate threshold',
description:
- 'Routes serving > 500 requests/period at < 50% cache hit AND at least 20% GET traffic. Each uncached GET request reaches the function, costing edge requests + function duration. Routes that are mostly POST/PUT/DELETE (Server Actions, mutations) are skipped — 0% cache is correct behavior there. Routes with missing method-share data are gated instead of launched. Auth-gated routes are disqualified separately.',
+ 'Routes serving > 500 requests/period at < 50% cache hit AND at least 20% GET traffic. Each uncached GET request reaches the function, costing CDN requests + function duration. Routes that are mostly POST/PUT/DELETE (Server Actions, mutations) are skipped — 0% cache is correct behavior there. Routes with missing method-share data are gated instead of launched. Auth-gated routes are disqualified separately.',
};
/**
diff --git a/skills/vercel-optimize/lib/scanners/force-dynamic.mjs b/skills/vercel-optimize/lib/scanners/force-dynamic.mjs
index 746cafd..e70d617 100644
--- a/skills/vercel-optimize/lib/scanners/force-dynamic.mjs
+++ b/skills/vercel-optimize/lib/scanners/force-dynamic.mjs
@@ -5,7 +5,7 @@ export const metadata = {
billingDimension: 'function-duration',
trafficIndependent: false,
description:
- "force-dynamic disables static + ISR rendering. The route runs the function on every request. Sometimes necessary (cookies, headers, real-time data), often a habit that costs function-duration and edge-requests at scale.",
+ "force-dynamic disables static + ISR rendering. The route runs the function on every request. Sometimes necessary (cookies, headers, real-time data), often a habit that costs function duration and CDN requests at scale.",
fix:
"Audit the route. If dynamic behavior comes from cookies()/headers()/searchParams, force-dynamic may be redundant — Next infers dynamic automatically. Consider revalidate / 'use cache' / generateStaticParams if any portion can be pre-rendered.",
citations: [
diff --git a/skills/vercel-optimize/lib/scanners/middleware-broad-matcher.mjs b/skills/vercel-optimize/lib/scanners/middleware-broad-matcher.mjs
index 1ab1bee..38766fd 100644
--- a/skills/vercel-optimize/lib/scanners/middleware-broad-matcher.mjs
+++ b/skills/vercel-optimize/lib/scanners/middleware-broad-matcher.mjs
@@ -5,7 +5,7 @@ export const metadata = {
billingDimension: 'edge-requests',
trafficIndependent: true,
description:
- 'middleware.ts without a config.matcher (or matcher: ["/(.*)"]) runs on every request including _next/static, _next/image, favicon.ico, and image asset fetches. Edge-request cost scales accordingly.',
+ 'middleware.ts without a config.matcher (or matcher: ["/(.*)"]) runs on every request including _next/static, _next/image, favicon.ico, and image asset fetches. CDN request cost scales accordingly.',
fix:
'Scope the matcher to actual application paths. Example: matcher: ["/((?!_next/static|_next/image|favicon.ico|.*\\\\.(?:svg|png|jpg|jpeg|gif|webp)$).*)"]',
citations: [
diff --git a/skills/vercel-optimize/references/candidates.md b/skills/vercel-optimize/references/candidates.md
index 9bcc87f..0265b3b 100644
--- a/skills/vercel-optimize/references/candidates.md
+++ b/skills/vercel-optimize/references/candidates.md
@@ -94,7 +94,7 @@ Observability Events line item exceeds 20% of total billed cost. High share usua
- **Scope**: account
- **Source citation**: `vercel-optimize gate threshold`
-When BotID is disabled AND there is evidence (observed bot bandwidth share, edge cost, or substantial request volume) that bot traffic is non-trivial. Bot traffic inflates edge request counts without delivering user value; staged bot protection can reduce waste on bot-heavy projects. Skipped on quiet projects with no bot evidence — the recommendation would be noise.
+When BotID is disabled AND there is evidence (observed bot bandwidth share, CDN request cost, or substantial request volume) that bot traffic is non-trivial. Bot traffic inflates CDN request counts without delivering user value; staged bot protection can reduce waste on bot-heavy projects. Skipped on quiet projects with no bot evidence — the recommendation would be noise.
---
@@ -160,7 +160,7 @@ Routes with p95 function duration above 500ms at meaningful traffic (>=1,400 inv
- **Scope**: route
- **Source citation**: `vercel-optimize gate threshold`
-Routes serving > 500 requests/period at < 50% cache hit AND at least 20% GET traffic. Each uncached GET request reaches the function, costing edge requests + function duration. Routes that are mostly POST/PUT/DELETE (Server Actions, mutations) are skipped — 0% cache is correct behavior there. Routes with missing method-share data are gated instead of launched. Auth-gated routes are disqualified separately.
+Routes serving > 500 requests/period at < 50% cache hit AND at least 20% GET traffic. Each uncached GET request reaches the function, costing CDN requests + function duration. Routes that are mostly POST/PUT/DELETE (Server Actions, mutations) are skipped — 0% cache is correct behavior there. Routes with missing method-share data are gated instead of launched. Auth-gated routes are disqualified separately.
---
diff --git a/skills/vercel-optimize/references/docs-library.json b/skills/vercel-optimize/references/docs-library.json
index ad4e330..2e677c2 100644
--- a/skills/vercel-optimize/references/docs-library.json
+++ b/skills/vercel-optimize/references/docs-library.json
@@ -205,11 +205,17 @@
},
{
"url": "https://vercel.com/docs/manage-cdn-usage",
- "topic": "Vercel Edge Network bandwidth — Fast Data Transfer, included quotas, overage pricing",
+ "topic": "CDN pricing and usage — Fast Data Transfer, Fast Origin Transfer, CDN Requests (formerly Edge Requests), included quotas, overage pricing",
"appliesTo": ["large_static_asset", "uncached_route"],
"applicableFrameworks": ["*"]
},
{
+ "url": "https://vercel.com/docs/pricing/flat-rate-cdn",
+ "topic": "Flat Rate CDN — fixed monthly tier covering CDN Requests and Fast Data Transfer on Pro, tier changes at the next billing cycle",
+ "appliesTo": ["platform_bot_protection", "large_static_asset", "uncached_route", "cache_header_gap"],
+ "applicableFrameworks": ["*"]
+ },
+ {
"url": "https://vercel.com/docs/functions/runtimes/edge-runtime",
"topic": "Vercel Edge Runtime — supported APIs, constraints, incompatible modules (node:* builtins, native deps)",
"appliesTo": ["edge_heavy_import", "cold_start"],
diff --git a/skills/vercel-optimize/references/doctrine.md b/skills/vercel-optimize/references/doctrine.md
index 91428a3..018e397 100644
--- a/skills/vercel-optimize/references/doctrine.md
+++ b/skills/vercel-optimize/references/doctrine.md
@@ -101,5 +101,5 @@ The skill is bounded to runtime cost and performance optimization on Vercel-host
- **Deployment artifact size** in isolation. Bundle size matters only when it shows up as runtime cost (cold start, FDT) or performance (LCP, INP). If the only effect is "the .next directory is large," it's not in scope.
- **Build-time issues without runtime impact.** Slow builds, build-cache misses, monorepo build fan-out — these only enter scope when they show up as Build Minutes billing pressure (then they go through the `build-minutes-fanout` gate). A 6-minute build that completes successfully and ships a small artifact is not a target.
-- **Security advisories and credential rotation.** RCE in `next-mdx-remote`, leaked env vars, OIDC vs explicit-key auth hygiene — refer to a security skill, not this one. Exception: when a security setting is also a documented cost lever (BotID = bot traffic = edge cost), it enters via the `platform_bot_protection` gate.
+- **Security advisories and credential rotation.** RCE in `next-mdx-remote`, leaked env vars, OIDC vs explicit-key auth hygiene — refer to a security skill, not this one. Exception: when a security setting is also a documented cost lever (BotID = bot traffic = CDN request cost), it enters via the `platform_bot_protection` gate.
- **Commercial / billing-process trivia.** Discount sliders, seat reconciliation, contract renewal mechanics. The skill can quantify which SKU is expensive; it does not negotiate.
diff --git a/skills/vercel-optimize/references/playbooks/README.md b/skills/vercel-optimize/references/playbooks/README.md
index 35e7d99..2337458 100644
--- a/skills/vercel-optimize/references/playbooks/README.md
+++ b/skills/vercel-optimize/references/playbooks/README.md
@@ -32,7 +32,7 @@ Each playbook is a Markdown file with a fixed shape so the recommender can parse
# {Profile name}
## Typical billing shape
-(Which dimensions dominate — e.g., "Edge Requests > Function Duration > Image Optimization")
+(Which dimensions dominate — e.g., "CDN Requests > Function Duration > Image Optimization")
## Priority patterns
(Ordered list of patterns this profile particularly benefits from)
diff --git a/skills/vercel-optimize/references/playbooks/ai-application.md b/skills/vercel-optimize/references/playbooks/ai-application.md
index 038bf09..ea91a73 100644
--- a/skills/vercel-optimize/references/playbooks/ai-application.md
+++ b/skills/vercel-optimize/references/playbooks/ai-application.md
@@ -1,10 +1,10 @@
# AI application
-LLM-backed apps, agents, code-sandbox tools, RAG pipelines. Cost shape is dominated by per-token AI Gateway spend and Sandbox active-compute time, not edge requests or function duration. Many AI customers also have a SaaS surface (auth, dashboards), but the cost lever lives upstream of the dashboard.
+LLM-backed apps, agents, code-sandbox tools, RAG pipelines. Cost shape is dominated by per-token AI Gateway spend and Sandbox active-compute time, not CDN requests or function duration. Many AI customers also have a SaaS surface (auth, dashboards), but the cost lever lives upstream of the dashboard.
## Typical billing shape
-AI Gateway > Sandbox Active Compute > Function Duration > Function Invocations. Edge Requests usually quiet; ISR rarely applies. Observability Events can climb fast if every tool-call span is captured at full fidelity.
+AI Gateway > Sandbox Active Compute > Function Duration > Function Invocations. CDN Requests usually quiet; ISR rarely applies. Observability Events can climb fast if every tool-call span is captured at full fidelity.
## Priority patterns
diff --git a/skills/vercel-optimize/references/playbooks/api-service.md b/skills/vercel-optimize/references/playbooks/api-service.md
index 7cac110..9871ee7 100644
--- a/skills/vercel-optimize/references/playbooks/api-service.md
+++ b/skills/vercel-optimize/references/playbooks/api-service.md
@@ -4,7 +4,7 @@ Headless API backend. No UI routes. Often consumed by mobile apps, partner integ
## Typical billing shape
-Function Duration dominates (every request is a function invocation). Edge Requests scale with API traffic. External API costs matter when the service is a thin shim over third-party APIs (Stripe, Twilio, etc.).
+Function Duration dominates (every request is a function invocation). CDN Requests scale with API traffic. External API costs matter when the service is a thin shim over third-party APIs (Stripe, Twilio, etc.).
## Priority patterns
diff --git a/skills/vercel-optimize/references/playbooks/content-site.md b/skills/vercel-optimize/references/playbooks/content-site.md
index d4c1f68..6752cff 100644
--- a/skills/vercel-optimize/references/playbooks/content-site.md
+++ b/skills/vercel-optimize/references/playbooks/content-site.md
@@ -4,7 +4,7 @@ Documentation, blogs, knowledge bases, marketing-adjacent content with mostly st
## Typical billing shape
-Edge Requests dominate (every page view is an edge request; static assets even more). Image Optimization is often the #2 line item. Function Duration tends to be low — most pages should be static or ISR.
+CDN Requests dominate (every page view is a CDN request; static assets even more). Image Optimization is often the #2 line item. Function Duration tends to be low — most pages should be static or ISR. On Flat Rate CDN, CDN Requests and Fast Data Transfer are covered by a fixed tier, so see the Flat Rate CDN rule in `references/scoring.md` before framing request reductions as savings.
## Priority patterns
diff --git a/skills/vercel-optimize/references/playbooks/ecommerce.md b/skills/vercel-optimize/references/playbooks/ecommerce.md
index 0942a97..627bab5 100644
--- a/skills/vercel-optimize/references/playbooks/ecommerce.md
+++ b/skills/vercel-optimize/references/playbooks/ecommerce.md
@@ -4,7 +4,7 @@ Storefronts with cart, checkout, product catalogs. Often Stripe-integrated. Traf
## Typical billing shape
-Edge Requests dominate (catalog browsing, image asset traffic) → Image Optimization (product images) → Function Duration (cart/checkout APIs). ISR Reads matter when product pages use ISR.
+CDN Requests dominate (catalog browsing, image asset traffic) → Image Optimization (product images) → Function Duration (cart/checkout APIs). ISR Reads matter when product pages use ISR. On Flat Rate CDN, see the Flat Rate CDN rule in `references/scoring.md` before framing CDN request reductions as savings.
## Priority patterns
@@ -19,7 +19,7 @@ Edge Requests dominate (catalog browsing, image asset traffic) → Image Optimiz
- **Product images served raw.** `<img src={product.imageUrl}>` for hundreds of variants costs more than the rest of the bill combined. Always next/image.
- **`force-dynamic` on the storefront homepage.** Often added during development to test cart-state behavior, never removed. Audit ruthlessly.
- **Sequential Stripe calls.** "Create customer" → "create subscription" → "create invoice" is often three sequential awaits where two could run in parallel.
-- **Bot traffic on product search.** Marketing-driven traffic + bot traffic on search routes inflates edge request cost. Bot Protection often pays for itself within a month.
+- **Bot traffic on product search.** Marketing-driven traffic + bot traffic on search routes inflates CDN request cost. Bot Protection often pays for itself within a month on on-demand CDN pricing; on Flat Rate CDN, frame it as keeping usage inside the current tier.
## Cross-references
diff --git a/skills/vercel-optimize/references/playbooks/marketing.md b/skills/vercel-optimize/references/playbooks/marketing.md
index b9f8b6d..d1d71ef 100644
--- a/skills/vercel-optimize/references/playbooks/marketing.md
+++ b/skills/vercel-optimize/references/playbooks/marketing.md
@@ -4,12 +4,12 @@ Landing pages, lead-capture forms, A/B-tested variants, region-routed homepages.
## Typical billing shape
-Edge Requests dominate. Image Optimization is high (hero images, illustrations, product screenshots). Bandwidth matters for video content. Function Duration is usually low — most pages are static or ISR.
+CDN Requests dominate. Image Optimization is high (hero images, illustrations, product screenshots). Bandwidth matters for video content. Function Duration is usually low — most pages are static or ISR. On Flat Rate CDN, see the Flat Rate CDN rule in `references/scoring.md` before framing CDN request reductions as savings.
## Priority patterns
1. **Aggressive caching at the edge.** Marketing pages rarely change between campaign updates. `Cache-Control: public, s-maxage=86400, stale-while-revalidate=604800` keeps the CDN warm for 24h and stale-serves for a week.
-2. **Bot Protection.** Marketing campaigns attract competitor scrapers and bot traffic that inflates edge requests without delivering value. If edge cost is > $100/month and Bot Protection is disabled, this is almost always the top platform rec.
+2. **Bot Protection.** Marketing campaigns attract competitor scrapers and bot traffic that inflates CDN requests without delivering value. If billed CDN Requests cost is > $100/month and Bot Protection is disabled, this is almost always the top platform rec. On Flat Rate CDN, the cost case is staying inside the current tier, not a lower bill this cycle.
3. **ISR for content-driven sections.** Customer logos, testimonials, "latest blog post" widgets, pricing tables — anything coming from a CMS. Revalidate hourly or on webhook.
4. **A/B test logic at the edge, not in the page.** Edge Middleware for the variant assignment; cached static page per variant. Don't render the variant choice on every request.
5. **Defer all third-party JS post-hydration.** Analytics, chat widgets, marketing pixels, cookie banners. None of them block the LCP. Cite `vercel-react-best-practices:bundle-defer-third-party`.
diff --git a/skills/vercel-optimize/references/playbooks/saas.md b/skills/vercel-optimize/references/playbooks/saas.md
index 6337377..22968b5 100644
--- a/skills/vercel-optimize/references/playbooks/saas.md
+++ b/skills/vercel-optimize/references/playbooks/saas.md
@@ -1,10 +1,10 @@
# SaaS
-Multi-tenant applications with authenticated dashboards, settings, billing. Auth-gated by default. Traffic skews toward function duration (per-user data fetches) over edge requests.
+Multi-tenant applications with authenticated dashboards, settings, billing. Auth-gated by default. Traffic skews toward function duration (per-user data fetches) over CDN requests.
## Typical billing shape
-Function Duration dominates (every dashboard request runs the function fully — no edge caching for auth-gated content). Edge Requests grow with API surface. ISR rarely applies. Image Optimization rarely material.
+Function Duration dominates (every dashboard request runs the function fully — no edge caching for auth-gated content). CDN Requests grow with API surface. ISR rarely applies. Image Optimization rarely material.
## Priority patterns
diff --git a/skills/vercel-optimize/references/playbooks/sveltekit.md b/skills/vercel-optimize/references/playbooks/sveltekit.md
index e7ea0ad..656ebd4 100644
--- a/skills/vercel-optimize/references/playbooks/sveltekit.md
+++ b/skills/vercel-optimize/references/playbooks/sveltekit.md
@@ -9,7 +9,7 @@ config rather than per-route framework APIs.
## Typical billing shape
Function Duration dominates server-rendered routes (every `+page.server.ts`
-`load` + `+server.ts` POST handler runs as a function). Edge Requests grow
+`load` + `+server.ts` POST handler runs as a function). CDN Requests grow
with API surface (`+server.ts` and form actions). ISR is supported via the
adapter; when enabled, it converts to a cache_result HIT after first render.
Image Optimization is rarely a SvelteKit-specific lever (it's the same
diff --git a/skills/vercel-optimize/references/scanner-patterns.md b/skills/vercel-optimize/references/scanner-patterns.md
index 26ae4d1..b0650af 100644
--- a/skills/vercel-optimize/references/scanner-patterns.md
+++ b/skills/vercel-optimize/references/scanner-patterns.md
@@ -49,7 +49,7 @@ Total scanners: 15.
- **Billing dimension**: function-duration
- **Traffic-independent**: no (cold-path findings get dropped)
-**Description.** force-dynamic disables static + ISR rendering. The route runs the function on every request. Sometimes necessary (cookies, headers, real-time data), often a habit that costs function-duration and edge-requests at scale.
+**Description.** force-dynamic disables static + ISR rendering. The route runs the function on every request. Sometimes necessary (cookies, headers, real-time data), often a habit that costs function duration and CDN requests at scale.
**Fix.** Audit the route. If dynamic behavior comes from cookies()/headers()/searchParams, force-dynamic may be redundant — Next infers dynamic automatically. Consider revalidate / 'use cache' / generateStaticParams if any portion can be pre-rendered.
@@ -112,7 +112,7 @@ Total scanners: 15.
- **Billing dimension**: edge-requests
- **Traffic-independent**: yes (cold-path findings survive the doctrine drop)
-**Description.** middleware.ts without a config.matcher (or matcher: ["/(.*)"]) runs on every request including _next/static, _next/image, favicon.ico, and image asset fetches. Edge-request cost scales accordingly.
+**Description.** middleware.ts without a config.matcher (or matcher: ["/(.*)"]) runs on every request including _next/static, _next/image, favicon.ico, and image asset fetches. CDN request cost scales accordingly.
**Fix.** Scope the matcher to actual application paths. Example: matcher: ["/((?!_next/static|_next/image|favicon.ico|.*\\.(?:svg|png|jpg|jpeg|gif|webp)$).*)"]
diff --git a/skills/vercel-optimize/references/scoring.md b/skills/vercel-optimize/references/scoring.md
index a988493..d0ad763 100644
--- a/skills/vercel-optimize/references/scoring.md
+++ b/skills/vercel-optimize/references/scoring.md
@@ -48,7 +48,7 @@ When the project is on a Flex Commit and the report frames savings against contr
| Discountable (slider applies) | Non-discountable (raw rate) |
|---|---|
| Seats | Build CPU Minutes |
-| Edge Requests | Fluid Active CPU |
+| CDN Requests (formerly Edge Requests) | Fluid Active CPU |
| Fast Data Transfer | Fluid Provisioned Memory |
| Fast Origin Transfer | Raw Flex top-up |
| Image Optimization | |
@@ -57,9 +57,15 @@ When the project is on a Flex Commit and the report frames savings against contr
A recommendation that targets a non-discountable SKU should never frame savings as a percentage of contract; frame as absolute magnitude only. Conversely, a discountable-SKU recommendation may surface "applies to contract burndown" in the magnitude phrase.
+### Flat Rate CDN
+
+Pro teams can pay for CDN usage with Flat Rate CDN: a fixed monthly tier that covers CDN Requests, Fast Data Transfer, Blob Data Transfer, Sandbox Data Transfer, and Observability Events generated from CDN requests. Usage above the tier for a billing cycle moves the team to a higher tier at the start of the next cycle; above the highest tier, it moves to on-demand pricing.
+
+When the billing data shows these resources covered by a Flat Rate CDN tier (for example, CDN Requests and Fast Data Transfer with usage but zero billed cost), do not frame a CDN request or data transfer reduction as a lower bill this cycle. Frame it as headroom inside the current tier, or as avoiding a move to a higher tier, and still report the performance impact. Cite `https://vercel.com/docs/pricing/flat-rate-cdn`.
+
**Why magnitudes:**
-- Traffic varies. A "20% reduction in edge requests" is exact at today's traffic and meaningless next quarter.
+- Traffic varies. A "20% reduction in CDN requests" is exact at today's traffic and meaningless next quarter.
- Pricing changes. Vercel's billing rates move; precise dollar projections rot.
- The user is smart. They'd rather see "hundreds of dollars per month" with a real metric backing it than `$340/mo` with a hand-wave behind it.
- The `$-strip` sanitizer enforces this at output time. Any `$N` literal that slips into customer-facing fields is replaced with "the billed cost" before rendering.
@@ -73,7 +79,7 @@ type ImpactLabel = {
// MAGNITUDE: cost recs
costMagnitude?: 'negligible' | 'small' | 'medium' | 'large' | 'very-large';
costPhrase?: string;
- billingDimension?: string; // 'Edge Requests' | 'Function Duration' | ...
+ billingDimension?: string; // 'CDN Requests' | 'Function Duration' | ...
fractionReduced?: number; // 0.2 = ~20% — internal only, NOT rendered
};
```
@@ -194,11 +200,11 @@ The recommender selects 0-2 playbooks based on the project's `stack.applicationP
| Application profile | Likely top dimensions | Apply playbooks |
|---|---|---|
| `ai-application` (AI SDK, AI Gateway, Sandbox usage) | AI Gateway, Sandbox Active Compute, Function Duration | `playbooks/ai-application.md` |
-| `ecommerce` (Stripe, Shopify, cart components) | Edge Requests, Function Duration | `playbooks/ecommerce.md` |
+| `ecommerce` (Stripe, Shopify, cart components) | CDN Requests, Function Duration | `playbooks/ecommerce.md` |
| `saas` (auth, dashboards, multi-tenant) | Function Duration, Bandwidth | `playbooks/saas.md` |
-| `api-service` (mostly API routes, no UI) | Function Duration, Edge Requests | `playbooks/api-service.md` |
-| `content-site` (blog, docs, mostly static) | Edge Requests, Image Optimization | `playbooks/content-site.md` |
-| `marketing` (landing pages, A/B tests) | Edge Requests, ISR Reads | `playbooks/marketing.md` |
+| `api-service` (mostly API routes, no UI) | Function Duration, CDN Requests | `playbooks/api-service.md` |
+| `content-site` (blog, docs, mostly static) | CDN Requests, Image Optimization | `playbooks/content-site.md` |
+| `marketing` (landing pages, A/B tests) | CDN Requests, ISR Reads | `playbooks/marketing.md` |
`ai-application` is checked first in `inferPlaybook()` — an AI-heavy SaaS or AI commerce app shares the AI playbook's billing shape (AI Gateway dominant) and gotchas, not the dashboard or cart-checkout patterns.
diff --git a/skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md b/skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md
index 658f2ec..8808e76 100644
--- a/skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md
+++ b/skills/vercel-optimize/references/support-topics/bot-protection-product-guardrails.md
@@ -10,13 +10,13 @@ maxBriefChars: 800
---
## Investigation Brief
-Bot Protection recommendations must be grounded in observed automated traffic or meaningful edge-request scale.
+Bot Protection recommendations must be grounded in observed automated traffic or meaningful CDN request scale.
## Evidence To Check
-Check bot bandwidth share, edge request volume, existing WAF managed rules, and whether BotID or Bot Protection is already enabled. Prefer a staged Log to Challenge or Deny path for rules whose false-positive risk is not proven.
+Check bot bandwidth share, CDN request volume, existing WAF managed rules, and whether BotID or Bot Protection is already enabled. Prefer a staged Log to Challenge or Deny path for rules whose false-positive risk is not proven.
## Do Not Recommend When
-Do not recommend disabling Vercel security products to reduce cost. Do not recommend Bot Protection for quiet projects with no bot evidence.
+Do not recommend disabling Vercel security products to reduce cost. Do not recommend Bot Protection for quiet projects with no bot evidence. On Flat Rate CDN, frame fewer CDN requests as tier headroom, not a lower bill.
## Verification
State the observed bot share or scale signal, current protection state, and any existing log, challenge, deny, or BotID check.
diff --git a/skills/vercel-optimize/references/voice.md b/skills/vercel-optimize/references/voice.md
index aa927f0..a3d15fc 100644
--- a/skills/vercel-optimize/references/voice.md
+++ b/skills/vercel-optimize/references/voice.md
@@ -56,7 +56,7 @@ Use these spellings:
| `Web Analytics` | `Vercel Analytics` |
| `Hobby`, `Pro`, `Enterprise` | `hobby`, `pro`, `enterprise` as plan names |
-Mirror billing names from the user's dashboard. If a dashboard still says `Edge Requests`, use `Edge Requests`; do not rename it.
+Mirror billing names from the user's dashboard. `Edge Requests` was renamed `CDN Requests` in September 2026 (same metric, pricing, and limits). Say `CDN Requests`; if the billing data for the window still says `Edge Requests`, note once that it is the same metric now called `CDN Requests`.
## Recommendation shape