Loading
Knocking on the endpoint…
We ask it what it charges, read its catalogue entry, apply the policy, and then ask it again to see whether the price held. That is two round trips to somebody else’s server, so a few seconds is normal and a slow answer is a fact about them rather than about this page.
Walks a whole purchase in the order a buyer asks the questions, stopping at the first that objects. Nothing is signed and nothing is spent. The payment check asks the narrower question, about a payment you have already decided on.
Over the endpoints WE have knocked on, which is our reach and not the catalogue. A disagreement is between two statements by the SAME party, their listing and their endpoint, so it is theirs to explain and never ours to resolve; it is not evidence of fraud and a seller may simply have moved their payee and not relisted. `comparable` is the denominator: an endpoint that names no payee, or whose listing names none, cannot disagree and is not counted either way.
Which endpoints, and whose, needs a plan. Any single endpoint you name is free: search for it above and its own reading is on the row.
A careful buyer stops at "Is the thing I want to buy actually there?" Nothing answered: the path the catalogue names is not served. There is nothing to buy here today.
One knock has failed, on 2026-10-27, and 1 more are needed before we would call it down. A single failure is a reason to ask again, not a finding.
One mark is one knock, not a span of time. We knock a working endpoint about once a day and back off on one that has been down a long time, so a gap here is where we did not look.
A filled rehearsal is always a live knock, so it may ask you to wait a moment, and it is not written to the record above: two different questions in one series would look like a price that moved.
The catalogue lists this endpoint as a template, so we asked with company_id_or_domain left unfilled. Availability holds either way. The price may be the generic one rather than the price of the call you mean to make.
Questions after that one were still asked, on purpose: stopping at the first objection would hide a second, and a buyer who fixes this one deserves to know what is behind it. Nothing financial happened either way. Not one of these five signs or spends anything.
Asked just now. We knock at most once a minute per endpoint, shared by everybody, because our own user agent promises not to be a load.
The half that settles those is a real payment from your own wallet, which is not built yet. When it is, the money goes to the seller and never through us.