Add wayleave to Open Source & SDKs - #537
Open
gibrancorbin11-hub wants to merge 1 commit into
Open
Conversation
Web Bot Auth verification and pricing gate for agent traffic. Returns an x402-shaped 402; settlement is a pluggable stub, stated explicitly in the entry so it isn't mistaken for a facilitator or payment SDK.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one entry to Open Source & SDKs.
wayleave is zero-dependency Node/Express middleware for the gate side of agent commerce rather than the settlement side. It verifies Web Bot Auth signatures (RFC 9421 profile, Ed25519) against key directories you configure, classifies each request into verified / declared / suspected / human lanes, applies per-lane policy, and returns an x402-shaped 402 with a price on routes you choose. Humans never see a paywall.
Scope, stated plainly: settlement is a pluggable stub. The 402 challenge and the payment-proof check work; no payment network is wired. The entry says so explicitly, because most items in this section are facilitators or SDKs that actually move funds, and I don't want it read as one of those.
If a verification-and-pricing layer without settlement is out of scope for this list, please just close this — no hard feelings, and a pointer to where it would belong instead would be genuinely useful.
MIT, 22 adversarial tests (forged signatures from stolen keyids, tampered requests, expired signatures, replay-farming windows, a metering hook that throws mid-request). On npm as
wayleave.