See the traffic.
Record requests by route and classification. Separate signed agents, self-declared crawlers and suspected automation.
Connect your app →OPEN-SOURCE AGENT INFRASTRUCTURE
Know what’s crossing your app.
Observe agent traffic. Control access.
Charge payment-ready agents.
npm install wayleaveFree MIT middleware · Node 18+ · No runtime dependencies
Agent & suspected bot requests
1,284| Identity / signal | Route | Classification |
|---|---|---|
| search.example | /api/search | Verified |
| Declared crawler | /docs | Declared |
| Automation signals | /api/products | Suspected |
| research.example | /api/data | Verified |
| Browser-shaped | / | Unverified |
Illustrative traffic, not customer results. Only signed identities are cryptographically verified.
ONE GATE. THREE STEPS.
Record requests by route and classification. Separate signed agents, self-declared crawlers and suspected automation.
Connect your app →Apply allow, deny and rate-limit policies by lane and route. Start with no enforcement, then add rules deliberately.
Return a price on selected routes. Access can be released after payment verification through your configured provider.
A priced request is not earned revenue. Payment support depends on the agent and provider.
How payments work ↗FROM INSTALL TO FIRST REQUEST
No wallet or payment rules needed.
Signing in does not start a subscription. Hosted Meter terms are below.
import Wayleave from 'wayleave';
if (!process.env.WAYLEAVE_METER_KEY) {
throw new Error('Set WAYLEAVE_METER_KEY');
}
const gate = new Wayleave({
meter: {
apiKey: process.env.WAYLEAVE_METER_KEY,
},
});
// Mount before the routes you want to observe.
app.use(gate.express());No prices, blocking rules or rate limits configured. Add them when you’re ready.
STRAIGHTFORWARD PRICING
Request classification, signature verification, route policies and metering hooks in your application.
Get the npm package ↗A hosted ledger for traffic and confirmed settlement records, with CSV export and separate API keys.
Open the Meter →Optional 3-day trial requires a card. $49/month afterward unless canceled. Signing in alone does not start billing.
Cryptographic verification checks a signature against keys you trust. Self-declared and suspected traffic are classifications, not proof of an operator’s identity.
Browser-shaped traffic can include bots. For priced resources, use strict policies and your own trusted human check. Supported payments require a configured verifier; bank payouts are not available.
Read the security model ↗OBSERVE → CONTROL → MONETIZE