Unverified50% confidenceFactExact time
In 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.
1
Sources
50%
Confidence
Long-term
Relevance
9/23/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe core idea of the X402 protocol is to embed payment into the HTTP request process: the server returns a 402 status code with payment details, the agent signs an authorization from a crypto wallet, completes the payment, and retries the request.70% similarUnverifiedA 200 interface response and a successful page display do not mean the data was written correctly in the database; the UI layer cannot cover the blind spot of business data correctness.67% similarUnverifiedHTTP 503 indicates the server is temporarily unable to handle the request, 500 indicates a backend logic anomaly, and 404 indicates that the requested resource does not exist.58% similarVerifiedThe HTTP 200 status code only indicates that the server successfully received and processed the request; it does not represent correct execution of business logic, as a large number of business errors can be wrapped inside a 200 response body.57% similarUnverifiedThe x402 protocol attack surface includes Authorization Bypass, where an attacker may circumvent or forge payment authorization to achieve unauthorized transactions.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/942962API
curl https://kongchang.com/api/v1/knowledge/claims/942962MCP
get_claim(id=942962)