FAQ
Frequently asked questions
Wayleave (wayleave.dev) is infrastructure for the agentic web: build apps, identify and control AI agent traffic, and meter and monetize it — humans free, agents identified.
Questions
What is Wayleave?
Wayleave is developer infrastructure for AI agent traffic: open-source middleware and hosted services that identify AI agents, enforce access policies, meter every crossing and price non-human access with HTTP 402. It is at wayleave.dev.
Is Wayleave related to UK wayleave agreements?
No. Wayleave.dev is a software platform for AI agent traffic. The name borrows the idea of a right of way — a wayleave — for agents crossing your app.
How does Wayleave identify AI agents?
By Ed25519 HTTP Message Signatures (RFC 9421, compatible with Web Bot Auth) checked against key directories you trust, plus classification of unsigned traffic into declared agent, suspected bot and human lanes.
Can Wayleave charge AI agents?
Yes. Priced routes return HTTP 402 Payment Required with an x402-shaped challenge. Humans are never charged, and Wayleave takes 0%.
Is Wayleave open source?
The middleware is the open-source wayleave package on npm, with zero dependencies.
What are Wayleave Build, Core and Meter?
Build takes an idea to a deployed app; Core handles identity, verification, classification, policies and HTTP 402; Meter is the dashboard for traffic, identities, routes, policies, revenue and logs.
Can a bot bypass Wayleave?
Wayleave prices disclosure; it does not detect concealment. A bot that sends a browser user-agent and accept-language header reaches the human lane — set strictPricedPaths: true on anything you charge for, so only a verified signature (or your own confirmHuman check) crosses a priced route.