How to publish x402 Bazaar metadata agents can use
A practical checklist for discoverable route descriptions, schemas, examples and settlement-backed indexing.
DIRECT ANSWER
Declare the official Bazaar discovery extension on each protected route, including a precise description, input schema and safe example. Use the current x402 v2 packages and a supported facilitator. CDP catalogs eligible routes after a successful settlement through its facilitator; publishing a field that merely says discoverable does not replace the required extension shape or settlement flow.
Key takeaways
- Discovery metadata must describe the callable resource, not just the provider homepage.
- Examples should be safe, representative and valid against the input schema.
- Indexing through CDP depends on a compatible route and completed facilitator flow.
Minimum useful metadata
An agent needs to know what the route does, how to call it and what kind of response to expect before considering payment. Use an action-oriented description, explicit method, MIME type, input properties, required fields and one public example. Avoid promotional claims that cannot be evaluated from the response.
| Field | Good practice |
|---|---|
| Description | Name the result and important limits |
| Input schema | Types, descriptions and required fields |
| Example | Safe public values that exercise the route |
| Price requirements | Current scheme, network, asset and amount |
Common indexing failures
Services can remain absent when they use x402 v1 extension shapes, add non-standard Bazaar fields, send the extension on the wrong route or never complete an eligible settlement through the expected facilitator. Validate the exact package version and facilitator base URL against current documentation rather than copying an older example.
Make directories more accurate
Publish a canonical docs URL and a machine-readable manifest where appropriate. Keep route descriptions stable enough to deduplicate, but update price and schema changes promptly. If a route is retired, return a clear status and remove it from discovery metadata instead of leaving a permanent broken entry.
Related directory entries
Sources and methodology
TOLL·402 distinguishes public claims, registry discovery, unpaid quote checks and settled paid-call verification. Sources below support the visible claims; presence in a registry is not treated as verification.
- x402 Bazaar documentation — Authoritative indexing and extension behavior.
- x402 seller quickstart — Current declaration examples.
- x402 issue 2207 — Reports missing extension responses and failed Bazaar indexing after successful CDP facilitator settlements.