Skip to main content
The Bazaar has no registration form. If a seller’s endpoint speaks x402 through this facilitator, it gets cataloged. This page describes how, and what a seller can do to shape what ends up in the listing.

​
The trigger

A listing is created (or updated) the first time the facilitator sees a PaymentRequirements object that includes describe metadata. That typically happens on the first /verify call, but it can also happen through a proactive /discovery/publish call the middleware makes at startup. Endpoints without describe still work — they just do not appear in search.

​
What gets stored

​
Signals collected over time

  • Last successful settlement timestamp.
  • Recent settlement count in a rolling window.
  • Rejection rate (from /verify failures).
These feed the ranker. See Search & Ranking.

​
Delisting

A listing is dropped when:
  • The endpoint has returned only resource_gone or non-402 errors for a configurable interval (default: 24 hours).
  • The seller explicitly calls DELETE /discovery/resources/:id.
  • The facilitator operator delists it (rare, for abuse).
Otherwise, listings persist indefinitely.

​
Seller responsibilities

  • Provide a describe block. Without it, cataloging is impossible.
  • Keep the describe block honest. Buyers filter by capability, and mismatched listings raise rejection rates and drop your rank.
  • Reject cleanly (return resource_gone on a removed endpoint) rather than 404, so the delister can find you.