Unverified50% confidenceFactExact time
Both 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.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/17/2026
First Seen
Valid until: 10/31/2026
Sources
Related Entities
Related Claims
UnverifiedIn 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.70% similarUnverifiedSending a forged X-PAYMENT header to the two endpoints returns 402 and a malformed_payment_header error from pay.openfacilitator.io65% similarUnverifiedThe 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.63% similarUnverifiedHTTPS traffic flowing through Cloudflare is decrypted and re-encrypted at its edge nodes, giving the service provider the technical capability to observe plaintext traffic.63% similarUnverifiedA considerable proportion of official portals return 403 errors or bot verification challenges to ordinary HTTP clients, and using curl or a basic requests library will be blocked at the first step.62% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053696API
curl https://kongchang.com/api/v1/knowledge/claims/1053696MCP
get_claim(id=1053696)