create-python-x402-facilitator-bazaar

Call declare_discovery_extension() with an input example, input_schema, and optional OutputConfig, then spread the result into your RouteConfig extensions dict. Register bazaar_resource_server_extension on your x402ResourceServer so the HTTP method is injected at runtime.

Use extract_discovery_info() with the payment payload and payment requirements, optionally setting validate=True. It returns a DiscoveredResource with the resource URL, HTTP method, and discovery info, or None if no Bazaar extension is present.

Yes, Bazaar discovery works with both frameworks. FastAPI uses x402ResourceServer with PaymentMiddlewareASGI, while Flask uses x402ResourceServerSync with the payment_middleware function; both register the same bazaar_resource_server_extension.

The body_type parameter distinguishes query-based extensions from body-based ones. The default None creates a query extension for GET, HEAD, or DELETE, while "json", "form-data", or "text" creates a body extension for POST, PUT, or PATCH routes.

The jsonschema package is only installed via the extensions extra. Install it with pip install "x402-avm[extensions]" or combine it with framework extras like "x402-avm[extensions,avm,fastapi]".

No, Bazaar discovery is chain-agnostic. The same metadata applies whether clients pay via Algorand (AVM), EVM, or SVM networks, so a single extension declaration works for multi-chain route configurations.