Sourced note
Your docs have a new first reader
Across the Vercel network, most traffic is now bot-originated, and on Vercel's own docs a large share of pageviews come from agents. The first reader of your docs and pricing page may be an agent working for someone else.
The numbers (as of 10 October 2026)
- In a post on 10 October 2026, Vercel's CEO Guillermo Rauch said that across the Vercel network, 58.18% of traffic over the last 30 days was bot-originated (a bot-traffic figure, not a count of AI agents), up from 32% in January 2024, and that more than 60% of deployments on Vercel are now agentic, up from about 3% in January 2026.
- In the same post he said up to 83% of pageviews on Vercel's own documentation sites come from agents, and the share rises the more the content is optimized for them.
- Vercel's agentic infrastructure post (first published 9 April 2026, since updated) says coding agents now initiate more than 50% of deployments on Vercel, as of September 2026, up from over 30% when the post first ran. These are Vercel's self-reported figures; no methodology is published.
What it changes for anyone selling software
The thing deciding whether your product gets picked may be an agent reading your docs on someone's behalf. If setup steps live in a video, limits sit in a PDF, or pricing needs a sales call, the agent may move on without leaving a visible bounce.
Agents that buy are arriving too: Shopify's Shop MCP (October 2026) lets any MCP-compatible agent search, build a cart and check out, with the shopper confirming before checkout completes. Being readable comes before being bought.
A plain-text audit (16 October 2026)
Three public pages were fetched as HTML, with scripts and styles stripped, and only the remaining text was read (no images, no client rendering). Plain-text audit, 16 October 2026 (Kuwait time).
| Page | How do I start? | What does it cost? |
|---|---|---|
| AI SDK introduction | Yes: generateText example and links into getting started | No: no prices on the page; only a footer "Pricing" link |
| AI SDK getting started (Next.js App Router) | Yes: Node 22+, pnpm create next-app, pnpm add ai @ai-sdk/react zod, AI_GATEWAY_API_KEY, route handler and useChat | No: it tells you to get an AI Gateway key, not what a request costs |
| Vercel AI Gateway overview | Yes: cURL and AI SDK snippets, "Choose how to start" | Partial: says AI Gateway adds zero markup to provider token prices and links to a Pricing page; no model prices on this page |
The getting-started page is the one an agent would use to ship. In plain text it answers setup. It does not answer cost. An agent that only has that page cannot decide whether the stack is affordable, and the footer Pricing link is not the answer either.
What I would fix first on a page like that: one short paragraph (or a table) with where prices live, whether the gateway adds markup, and a dated link to the live price list, in the same plain text as the install steps.
The check
- Split human from bot traffic on your docs.
- Read your most-visited docs page as plain text: no images, no scripts.
- If "how do I start and what does it cost" isn't answered in that text, an agent reading the page may never find it. Fix that page first.