Ontario Protocol.
Free parser · no wallet · no settlement

Debug an x402 Bazaar extension response before repeating the payment test.

Find out whether EXTENSION-RESPONSES is rejected, still processing, accepted, malformed, or missing. Ontario returns normalized remediation without echoing the captured header.

Run the free debuggerRun the full Bazaar checkOfficial Bazaar docs

What this tool catches

Rejected extensions

A normalized rejection state points you back to schema, route, and input/output parity.

Processing ambiguity

Processing is treated as pending evidence, not as a claim that the endpoint is already listed.

Unsafe input handling

Raw header contents are never returned. The tool is designed for provider-side evidence review, not payment execution.

Machine-readable API

The same bounded parser is available without the page:

curl -X POST https://ontarioprotocol.com/api/tools/x402-bazaar-extension-debugger \
  -H 'Content-Type: application/json' \
  -d '{"endpoint_url":"https://api.example.com/v1/paid","extension_responses":{"bazaar":{"status":"processing"}}}'

Response schema: ontario.x402_bazaar_extension_debugger.v1. It returns status and remediation, not the submitted header.

Trust boundary

Ontario provides readiness and trust signals based on observable endpoint behavior, manifest metadata, payment challenge behavior, report history, and public evidence. It does not guarantee endpoint safety, service quality, financial outcome, catalog placement, or future behavior.

What Ontario checks · What Ontario does not check · Provider quickstart