Skip to main content
The Bazaar is the discovery layer that sits alongside StellarX402’s facilitator. If x402 solves the question “how does a client pay for a resource once it has the URL,” the Bazaar solves the previous one: “how does the client find the URL in the first place.”

​
Why it exists

An agent that only knows how to pay for endpoints its operator has hardcoded is not much of an agent. Real autonomy needs a way for software to ask “is there anything out there that can do X, for less than Y, on a network I speak?” and get a machine-readable answer. That question is what the Bazaar answers.

​
What it catalogs

  • HTTP endpoints that respond with a valid 402 through this facilitator, using the describe metadata the seller declared.
  • MCP tools registered against the facilitator’s MCP discovery endpoint, treated as first-class citizens alongside HTTP endpoints.
Both are searchable through the same query API (/discovery/search) and can be filtered against the same criteria (/discovery/resources).

​
What is in a listing

Each cataloged resource carries:
  • A stable resource URI (URL for HTTP, tool name for MCP).
  • Payment terms: scheme, network, asset, amount (or price range for upto).
  • Discovery metadata the seller declared: title, description, input schema, tags.
  • Signals: last successful settlement time, recent volume, and, for MCP tools, invocation count.
The signals feed into ranking. See Search & Ranking.

​
What the Bazaar is not

  • Not a marketplace. No accounts, no seller registration, no reviews. If your endpoint speaks x402 through the facilitator, it is in.
  • Not authoritative. The catalog is eventually consistent with the endpoints it points at. If a seller changes their price, listings update within a few seconds. If a seller vanishes, listings expire from ranking within minutes.
  • Not a paywall around discovery. Search is free. Only payments cost.

​
Where next