Support pointed me here, since docs corrections are handled by the docs and engineering teams rather than a support case.
Two rows in the pricing table on /docs/limits disagree with the rest of the site by orders of magnitude.
Edge Config Reads
| Page | Rate |
|---|---|
/docs/limits |
$3.00 per 1,000 Reads |
/docs/edge-config/edge-config-limits |
$3.00/1,000,000 Reads |
/pricing |
Starting at $3 per 1M reads |
That is 1000x, and it is two pages to one.
Web Analytics Events
| Page | Rate |
|---|---|
/docs/limits |
$3.00 per 1,000 Events |
/pricing |
$3 per 100K events |
That is 100x.
What rules out a units-convention difference: the other rows in that same /docs/limits table match /pricing exactly. Image Optimization Cache Reads is $0.40 per 1M reads on both. The pages agree everywhere except these two cells.
To reproduce, both return output today:
curl -sL https://vercel.com/docs/limits | grep -oF '$3.00 per 1,000 Reads'
curl -sL https://vercel.com/pricing | grep -oF 'Starting at $3 per 1M reads'
Practical impact: a team sizing 100M Edge Config reads a month computes $300,000 off /docs/limits against roughly $300 at the real rate. That is the difference between adopting Edge Config for feature flags and rejecting it.