# Cross-link map: Features (/docs/build-output-api/features)

> From the Vercel docs graph (built 2026-09-21T05:26:59.511Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

## Semantically closest pages

- [How Vercel builds your application](https://vercel.com/docs/fundamentals/builds?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=semantic) — Learn how Vercel transforms your source code into optimized assets ready to serve globally.
- [Routing](https://vercel.com/docs/routing?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=semantic) — Learn how Vercel's CDN routes requests through firewall, project routes, and deployment routes before reaching your appl
- [React Router on Vercel](https://vercel.com/docs/frameworks/frontend/react-router?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=semantic) — Deploy React Router applications with SSR or SPA mode, then configure the Vercel preset, streaming, caching, and analyti
- [How requests flow through Vercel](https://vercel.com/docs/fundamentals/infrastructure?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=semantic) — Learn how Vercel routes, secures, and serves requests from your users to your application.
- [Advanced Configuration](https://vercel.com/docs/functions/configuring-functions/advanced-configuration?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=semantic) — Learn how to add utility files to the /api directory, and bundle Vercel Functions.

## Prerequisites

- [Build Output API](https://vercel.com/docs/build-output-api?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=prerequisite) — The Build Output API is a file-system-based specification for a directory structure that can produce a Vercel deployment

## This page links to (5)

- [Build Output Configuration](https://vercel.com/docs/build-output-api/configuration?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=outbound) — Learn about the Build Output Configuration file, which is used to configure the behavior of a Deployment.
- [Vercel Primitives](https://vercel.com/docs/build-output-api/primitives?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=outbound) — Learn about the Vercel platform primitives and how they work together to create a Vercel Deployment.
- [Services](https://vercel.com/docs/build-output-api/services?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=outbound) — Learn how a deployment with multiple services is structured in the Build Output API.
- [Static Configuration with vercel.json](https://vercel.com/docs/project-configuration/vercel-json?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=outbound) — Learn how to use vercel.json to configure and override the default behavior of Vercel from within your project.
- [Services routing](https://vercel.com/docs/services/routing?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=outbound) — Learn how Vercel routes public requests to services and how each service handles its own routes.

## Pages that link here (2)

By site: vercel-docs (2)

- [Build Output API](https://vercel.com/docs/build-output-api?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=inbound) — The Build Output API is a file-system-based specification for a directory structure that can produce a Vercel deployment
- [Cache Status and Reasons](https://vercel.com/docs/caching/cache-status?from=graph&source_path=%2Fdocs%2Fbuild-output-api%2Ffeatures&source_site=vercel-docs&relationship=inbound) — Understand the cache status and reason shown for each request in Vercel logs, and what causes a response to miss, bypass