Repository navigation
chore: @profullstack/x402-gateway 0.16.0 (one fetch reads the page) - #401
Merged
Merged
Conversation
A stale, spoofed or headless browser string now reads 20 pages an hour per address before the 402, so a person or an agent fetching one page gets it and a bulk crawl still pays. Declared AI crawlers are still charged on sight. New authenticate hook for sites with API keys. profullstack/x402-gateway#29 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan47 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 29 | LOW: 16
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Bumps @profullstack/x402-gateway to 0.16.0 (profullstack/x402-gateway#29), and @profullstack/throttle to 0.4.1 where present so there is one gateway copy. A plain one-shot fetch (no cookies, no JS) with a stale, spoofed or headless browser string got HTTP 402 on the first request. Now those strings read 20 pages an hour per address before the 402, so a person or an agent reading one page gets it and a bulk crawl still pays. Declared AI crawlers (GPTBot, ClaudeBot, CCBot) are still charged on sight; verified search crawlers are untouched. Lockfile only otherwise.
🤖 Generated with Claude Code