nitro.build valid

Nitro

Add server API routes to any Vite apps and deploy with zero configuration on your favorite hosting platform.

For agents: Nitro is a full-stack server framework adding API routes to Vite apps, with filesystem routing, renderers, caching and zero-config deployment across runtimes.

nitro server frameworkvite server routesserver api routesdeploymentfilesystem routingcaching

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T09:20:00.148Z. Cached copy · Source on nitro.build

# Nitro

> Add server API routes to any Vite apps and deploy with zero configuration on your favorite hosting platform.

## Docs

- [Home](https://nitro.build/raw/.md)
- [Introduction](https://nitro.build/raw/docs.md): Nitro is a full-stack server framework, compatible with any runtime and any deployment target.
- [Quick Start](https://nitro.build/raw/docs/quick-start.md): Start with a fresh Nitro project or adopt it in your current Vite project.
- [Nitro Renderer](https://nitro.build/raw/docs/renderer.md): Use a renderer to handle all unmatched routes with custom HTML or a templating system.
- [Routing](https://nitro.build/raw/docs/routing.md): Nitro supports filesystem routing to automatically map files to routes. Routes are compiled and code-split at build time, removing the need for a runtime router.
- [Nitro Server Entry](https://nitro.build/raw/docs/server-entry.md): Use a server entry to handle every request that no route matched.
- [Cache](https://nitro.build/raw/docs/cache.md): Nitro provides a caching system powered by ocache, with pluggable cache storage (in-memory, filesystem or the KV storage layer).
- [KV Storage](https://nitro.build/raw/docs/storage.md): Nitro provides a built-in storage layer that can abstract the filesystem, a database, or any other data source.
- [Assets](https://nitro.build/raw/docs/assets.md): Serve static files to clients and bundle files into your server for runtime access.
- [Configuration](https://nitro.build/raw/docs/configuration.md): Customize and extend Nitro defaults.
- [Database](https://nitro.build/raw/docs/database.md): Nitro provides a built-in and lightweight SQL database layer.
- [Lifecycle](https://nitro.build/raw/docs/lifecycle.md): Understand how Nitro runs and serves incoming requests to your application.
- [OpenAPI](https://nitro.build/raw/docs/openapi.md): Nitro can automatically generate an OpenAPI specification from your route handlers and serve interactive API documentation.
- [Plugins](https://nitro.build/raw/docs/plugins.md): Use runtime plugins to extend Nitro's runtime behavior.
- [Prerendering](https://nitro.build/raw/docs/prerendering.md): Render routes at build time and serve them as static assets.
- [Tasks](https://nitro.build/raw/docs/tasks.md): Nitro tasks allow one-off operations at runtime: named server-side actions such as database migrations, cache cleanup, or content syncing that you can run on demand, on a schedule, or from the CLI.
- [WebSocket](https://nitro.build/raw/docs/websocket.md): Nitro provides cross-platform WebSocket support powered by CrossWS and H3.
- [Modules](https://nitro.build/raw/docs/modules.md): Use modules to extend Nitro's build-time behavior.
- [CLI](https://nitro.build/raw/docs/cli.md): Nitro ships with a nitro command to develop, build, preview, and deploy your project.
- [Vite Integration](https://nitro.build/raw/docs/vite.md): Use Nitro as a Vite plugin to build full-stack applications, and choose the builder that bundles your server.
- [Serve
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=nitro.build · GET /v1/domain/nitro.build · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for nitro.build:
1. POST https://agentwebmap.com/v1/sites/nitro.build/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://nitro.build/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/nitro.build/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/nitro.build).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.