● Documentation

Overview

When an inbound webhook or HTTP request hits Vercel Eve on an unmapped route, Eve's underlying Nitro/H3 server drops it with a raw 404 before it reaches your agent. Because the request never enters the agent lifecycle, it leaves zero trace in Eve's terminal logs, local traces (.eve/traces/v1), or the Vercel Agent Runs dashboard. eve-preflight sits as a non-intrusive diagnostic proxy in front of Eve, intercepting incoming traffic to immediately pinpoint path misconfigurations, unhandled signatures, and silent drops.

Quick RunZero install needed

npx eve-preflight

Explore the Documentation

Getting Started

Two-terminal workflow, running against local Eve dev servers, and validating first requests.

CLI Reference

Complete reference of flags (-p, -t) and environment variables.

How It Works

Technical architecture: route schema discovery via eve info --json, proxying, and Slack checks.

Troubleshooting

Fix common errors like EADDRINUSE, upstream unreachable, or missing project context.