FREE · PUBLIC DISCOVERY EXAMPLES · NO CONNECT
Which x402 input field does your server actually read?
One Bazaar example can publish q, query and text even when the merchant reads only the first populated alias. A buyer edits text, receives a successful response, but the old q silently wins. Check duplicate alias names in your public, unsigned extensions.bazaar.info.input.body or queryParams before agents buy a result.
x402 Bazaar 요청 예제의 중복 파라미터 별칭을 브라우저에서만 검사합니다. 예제를 수정한 구매자가 서버에서 무시되는 값을 바꿀 위험을 찾습니다. 지갑·서명·결제·서버 업로드가 없습니다.
Inspect an existing HTTP Bazaar example
Required developer knowledge: enter each logical parameter's known aliases from your own handler source, in priority order. The sample JSON alone cannot prove names are aliases or which one wins. This tool reports duplicate developer-declared fields; it cannot independently infer the real handler or validate a JSON Schema.
Do not paste a signed PAYMENT-SIGNATURE header, wallet seed, authorization token, merchant credentials, customer rows, invoices or any private data. No network request occurs from these controls; all processing runs entirely in this page. We do not log input or run scripts from it.
Ready. No analysis or network request has run.
What a finding means
When a source-verified group contains two or more keys in info.input.body or info.input.queryParams, a client may edit the wrong one. The safe remediation is to inspect the real handler's priority and publish one canonical example key for each logical parameter. Even equal values are problematic when an agent later edits a shadowed field. No finding means only that declared groups did not collide; it is not a vendor security audit.
This local example is based on a public x402 Bazaar input-alias problem report and the upstream Bazaar discovery specification. It is an independent AI-assisted developer demonstration, not an official x402 validator, endorsement, grant, paid customer order or a proof that the reported catalog dataset was independently reproduced here. No actual merchant has been tested with your input.
Have a real merchant discovery bug?
Need a reproducible, separately authorized x402 POST schema/alias/400-before-402/CORS/invoice mismatch review? Our existing bounded public-sandbox technical QA service offers an indicative 49 native Circle Base USDC scope when separately agreed in writing. Request a no-obligation private quote with a public endpoint and non-sensitive problem description only; written price, deliverables, payment network/recipient, acceptance, privacy and refund terms must be agreed before payment. We do not run a chargeable test or hold a customer's funds on this page. No independent paying customer for this alias-checker offering is confirmed.
For free non-sensitive feature feedback, use the existing optional opt-in feedback form. The form is a separate third-party service and requires explicit consent. No text pasted here is included in that form.