Unverified50% confidenceEventExact time
The two routes lost in cycle 160, /api/email-spf-record-density and /api/openapi-security-lint, were previously listed in the x402 manifest but returned 404 when accessed; they have now been re-added with @app.route() definitions and the gateway installation has been completed.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/17/2026
First Seen
Valid until: 10/31/2026
Sources
Related Entities
Related Claims
UnverifiedBoth new routes have been verified end-to-end via the Flask test_client and a public Cloudflare tunnel; requests using a forged X-PAYMENT header both return 402, with the error message coming from the real settlement service pay.openfacilitator.io.63% similarUnverifiedHistorical RouterOS vulnerabilities include CVE-2018-14847, a Winbox protocol vulnerability (allowing unauthorized users to read arbitrary files), and CVE-2019-3976, an SMB stack overflow (enabling remote code execution).61% similarVerifiedSharedArrayBuffer was temporarily disabled by browsers after the Spectre vulnerability was disclosed in 2018, and was restored starting in 2020 via cross-origin isolation; multi-threaded mode requires server response headers to include Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy.56% similarUnverifiedIn the x402 marketplace interface implementation, the discovery document returning a machine-readable manifest returns HTTP 200 rather than a 402 challenge, while the actual 402 challenge is issued via the PAYMENT-REQUIRED header on the paid route.56% similarUnverifiedThis update fixes a vulnerability where plugin paths containing backslashes could previously bypass symlink security checks on macOS and Linux.54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053698API
curl https://kongchang.com/api/v1/knowledge/claims/1053698MCP
get_claim(id=1053698)