Skip to main content
Glama

What this address sells

list_x402_endpoints
Read-onlyIdempotent

WHICH ENDPOINTS A PAYEE SELLS, or which ones match some text. The sharpest check a payment can get is the endpoint being bought, and until this a caller had to know its URL by heart. Nearly every catalogued resource names a payee, and the catalogue holds tens of thousands of them. Every field is the SELLER’s own catalogue entry and never our reading of it, and a listing is not evidence that the endpoint answers — test_purchase knocks on it. priceUsd is their published price and priceRaw is the figure in the asset’s own base units; the two are different claims. FREE.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPart of a URL, matched case-insensitively.
limitNoDefault 20, capped at 100.
payeeNoAn address, to list what it sells.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
saysYesWhat the list is and is not: the seller’s own entries, and a listing is not evidence the endpoint answers.
countYesHow many came back, which is at most `limit` and says nothing about how many exist.
itemsYesOne per catalogued endpoint: `resource`, `payTo`, `priceUsd` and `priceRaw`, `asset`, `network`, the seller’s own `description` and when the listing was last seen — every one of those is the SELLER’s claim. `seenByUs` is the only field here that is OURS and the only one they cannot write: `state` (`answering`, `not-answering`, `unconfirmed` — one failure, which is a reason to ask again and not a finding — `seen-once`, or `never-knocked`), `answered` of `knocks`, `lastKnocked`, and an outage as a RANGE in `downAtLeastHours` / `downAtMostHours` rather than as a duration, because a stop happened somewhere between two knocks and that window is as wide as the gap between them. `never-knocked` and `seen-once` are statements about OUR reach, not about the seller, and today they cover most of the catalogue. The full timeline is on `test_purchase`.
cappedNoTRUE where the page came back full, so there are probably more; FALSE means the catalogue holds no further match and the list is everything we have, not just the first slice. This replaced a declared `limit` that the answer never carried — the envelope owns the paging keys — and it answers the question that field was for in one go.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources